← previous blocknext block →recent activity
Analyzing
Block #82,341,107
21 transactions · 16 stateful · 2026-06-19 16:14:55 UTC
Parallelism
90/100
Blocked
19%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #82,341,107 · 21 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
2w05w06w18w119w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xee9f5f19…f82f
0x34b655…2a6f
4 touches
1 conflict
0x6eac5a5d…1730
0x34b655…2a6f
4 touches
1 conflict
0x5581d709…ab77
0x2a68ba…90c5
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x4fa3b95a…880d
0x34b655…2a6f
2 touches
0 conflicts
0x8c84e7fe…afbd
0x34b655…2a6f
2 touches
0 conflicts
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: Perpl
1 conflict on slot 0xee9f5f1936…d6f82f
Audit this contract →
← previous block·next block →recent activity