Transaction

Hash
d14980ee049d2c60e1985ace8e2feef12a32a5e01b62e78d98d17eed26ed9482
Block
531962 · 2018-05-26 16:25 · 308,884 confirmations
Data
poll-vote
Size
327 bytes
Fee
329 sats (1.00611615 sat/B)

voted in poll 2154d

Should we be worried about a 51% attack on BCH? Please elaborate your answer:)

No

Not economically viable to 51% attack Bitcoin otherwise it would have already happened.

Inputs (1)

Index
0
Previous Output
304402205e01481eb0d91a0f211682e9debfca2c8d75f6dd90db7aebc74f0107694792f102200f2e1b634a9eecfc93bb75924e76b8b91af5a6335e742a04b1e9ea82c54a276b41 026ff29f38ca1998b6dfc4fe6ee961c762cd248a950aa7d4a3c2a8b3dc27948ff5

Outputs (2)

Index
0
Type
OP_RETURN
OP_RETURN 6d14 479d35637edfc1c03ea7430874023791f0f7c5a5f2290b9ec4b330ab58098e05 4e6f742065636f6e6f6d6963616c6c7920766961626c6520746f203531252061747461636b20426974636f696e206f746865727769736520697420776f756c64206861766520616c72656164792068617070656e65642e20
Index
1
OP_DUP OP_HASH160 07378be9b36fe9b5f32322eb073a6306edea8184 OP_EQUALVERIFY OP_CHECKSIG

Raw

0100000001abed0d88080f7970f84d68655bc8e77a89f7e297026c2bfa60b680dc6e8fbbb3010000006a47304402205e01481eb0d91a0f211682e9debfca2c8d75f6dd90db7aebc74f0107694792f102200f2e1b634a9eecfc93bb75924e76b8b91af5a6335e742a04b1e9ea82c54a276b4121026ff29f38ca1998b6dfc4fe6ee961c762cd248a950aa7d4a3c2a8b3dc27948ff5ffffffff0200000000000000007f6a026d1420479d35637edfc1c03ea7430874023791f0f7c5a5f2290b9ec4b330ab58098e054c584e6f742065636f6e6f6d6963616c6c7920766961626c6520746f203531252061747461636b20426974636f696e206f746865727769736520697420776f756c64206861766520616c72656164792068617070656e65642e20776d1600000000001976a91407378be9b36fe9b5f32322eb073a6306edea818488ac00000000