← previous blocknext block →recent activity
Analyzing
Block #82,524,251
20 transactions · 16 stateful · 2026-06-20 12:36:42 UTC
Parallelism
70/100
Blocked
38%
Avg conflicts / tx
0.8
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #82,524,251 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w113w014w116w217w318w419w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0xe59df86b…a00c
0x34b655…2a6f
8 touches
6 conflicts
0x1d3dac50…4731
0x34b655…2a6f
8 touches
6 conflicts
0x9966da31…0d0f
0x34b655…2a6f
6 touches
3 conflicts
0x86977b3d…a9c4
0x34b655…2a6f
6 touches
3 conflicts
0x62341e2a…2d78
0x34b655…2a6f
6 touches
3 conflicts
0xf22acca0…bdaa
0x34b655…2a6f
6 touches
3 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
15 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity