← previous blocknext block →recent activity
Analyzing
Block #84,572,029
10 transactions · 7 stateful · 2026-06-30 00:26:30 UTC
Parallelism
70/100
Blocked
43%
Avg conflicts / tx
0.3
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,572,029 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w07w18w29w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x05a7428b…ddf3
0x34b655…2a6f
4 touches
1 conflict
0x9a3068dd…18f0
0x34b655…2a6f
4 touches
1 conflict
0xbbb9fa77…d121
0x34b655…2a6f
4 touches
1 conflict
0xff6a6ba1…10c1
0x34b655…2a6f
4 touches
1 conflict
0x086db8fc…0024
0x34b655…2a6f
2 touches
0 conflicts
0x1232592b…a7d6
0x34b655…2a6f
2 touches
0 conflicts
0x1302cd54…e32e
0x34b655…2a6f
2 touches
0 conflicts
0x20079932…08b5
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 0x05a7428b79…6cddf3
Audit this contract →
← previous block·next block →recent activity