I noticed that Blockonomics not too long ago rolled out a local textual content search replace that lets customers question plaintext strings embedded in OP_RETURN straight from the search bar, moderately than needing a particular tx hash or tackle first.
From a utility standpoint, that is nice for pulling up order IDs or knowledge notarizations shortly. Nevertheless, from a technical perspective, indexing arbitrary strings on a public ledger looks as if it may get extremely heavy.
Does anybody know the way block explorers sometimes deal with the underlying structure for plaintext string indexing?
