← previous blocknext block →recent activity
Analyzing
Block #84,495,993
14 transactions · 14 stateful · 2026-06-29 15:58:57 UTC
Parallelism
71/100
Blocked
21%
Avg conflicts / tx
0.29
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,495,993 · 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
2w03w14w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb3975d93…b4a2
0x34b655…2a6f
6 touches
3 conflicts
0x3732c6c9…ded6
0x34b655…2a6f
4 touches
1 conflict
0x9a6af86a…4734
0x34b655…2a6f
4 touches
1 conflict
0xaa0fd315…db75
0x34b655…2a6f
4 touches
1 conflict
0xe99d8e68…a16e
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x2328941c…84d3
0x34b655…2a6f
4 touches
1 conflict
0xe02484a6…c32e
0xc8689a…ee79
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
3 conflicts on slot 0xb3975d9364…28b4a2
Audit this contract →
← previous block·next block →recent activity