0.0s
buffered ahead
—
read rate
0
transactions fetched
0 KB
pulled from ledger
Fragments
What is happening
- The index gives a fragment's byte range — never its bytes.
- That range maps to a run of transactions, each holding 1019 bytes of memo.
- The browser pulls them from a public node by hash, in parallel.
- Payloads are concatenated, trimmed, and checked against SHA-256.
- The fragment goes into a
SourceBuffer, and the decoder plays it.