← previous blocknext block →recent activity
Analyzing
Block #82,280,374
23 transactions · 19 stateful · 2026-06-19 09:29:49 UTC
Parallelism
91/100
Blocked
16%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #82,280,374 · 23 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w07w112w114w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd8dd03ce…dc8d
0x2a68ba…90c5
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0x9cc13b7b…c0ac
0xa6afd3…d132
4 touches
1 conflict
0x0e9b20a6…2a09
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x79f94908…8616
0x34b655…2a6f
4 touches
1 conflict
0xaadd6d85…a1bd
0x065c9d…c394
3 touches
1 conflict
0x6a6fc5ec…f403
0x065c9d…c394
3 touches
1 conflict
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Kuru Exchange: MarginAccount
1 conflict on slot 0xd8dd03ce37…9cdc8d
Audit this contract →
← previous block·next block →recent activity