This OP_RETURN proves that size limits are mempool policies, not consensus rules. Broadcast normally via Bitcoin RPC, not out-of-band. Economic incentives matter more than arbitrary byte limits. Mempool filters can't prevent data storage on Bitcoin. See also dust tx 199e6d98c300546a642803a2ffb849dae7dc7b8f9a0df88163cd9fc99033d3c5 for another non-standard example. npub1zmc6qyqdfnllhnzzxr5wpepfpnzcf8q6m3jdveflmgruqvd3qa9sjv7f60
| kind | human |
|---|---|
| block | 907,594 — 2025-07-28 17:23 UTC |
| transaction | 43f75a70b81b309bf72791ee8c455433a80332f6f05d5ebd7f4c015c58c294cd (output 1) |
| explorers | blockstream.info ↗ · mempool (emzy mirror) ↗ |
| payload size | 429 bytes |
| on chain | looking up the transaction… |
| share | post on X ↗ · permalink · card image ↗ |
| raw payload | 54686973204f505f52455455524e2070726f76657320746861742073697a65206c696d69747320617265206d656d706f6f6c20706f6c69636965732c206e6f7420636f6e73656e7375732072756c65732e2042726f616463617374206e6f726d616c6c792076696120426974636f696e205250432c206e6f74206f75742d6f662d62616e642e2045636f6e6f6d696320696e63656e7469766573206d6174746572206d6f7265207468616e206172626974726172792062797465206c696d6974732e204d656d706f6f6c2066696c746572732063616e27742070726576656e7420646174612073746f72616765206f6e20426974636f696e2e2053656520616c736f2064757374207478203139396536643938633330303534366136343238303361326666623834396461653764633762386639613064663838313633636439666339393033336433633520666f7220616e6f74686572206e6f6e2d7374616e64617264206578616d706c652e206e707562317a6d633671797164666e6c6c686e7a7a7872357770657066706e7a63663871366d336a647665666c6d67727571766433716139736a7637663630 |