← previous blocknext block →recent activity
Analyzing
Block #82,707,064
14 transactions · 12 stateful · 2026-06-21 09:00:10 UTC
Parallelism
71/100
Blocked
50%
Avg conflicts / tx
0.71
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #82,707,064 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w06w17w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb99958f6…ccf0
0x34b655…2a6f
8 touches
6 conflicts
0x2d8243b9…337b
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0x08913286…f0df
0x34b655…2a6f
4 touches
1 conflict
0x08cc68a2…2a59
0x34b655…2a6f
4 touches
1 conflict
0x26274321…3ad4
0x34b655…2a6f
4 touches
1 conflict
0x296f5c86…632b
0x34b655…2a6f
4 touches
1 conflict
0x426a6369…c556
0x34b655…2a6f
4 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: Perpl
6 conflicts on slot 0xb99958f6c8…c6ccf0
Audit this contract →
← previous block·next block →recent activity