← previous blocknext block →recent activity
Analyzing
Block #84,333,589
14 transactions · 13 stateful · 2026-06-28 21:56:11 UTC
Parallelism
71/100
Blocked
23%
Avg conflicts / tx
0.21
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,333,589 · 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
3w05w111w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9a3068dd…18f0
0x34b655…2a6f
4 touches
1 conflict
0x9a3068dd…18f1
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x3699265f…a82f
0x34b655…2a6f
4 touches
1 conflict
0x652bc0f0…6faf
0x34b655…2a6f
4 touches
1 conflict
0x92793b0e…b68e
0x34b655…2a6f
4 touches
1 conflict
0x23840716…10e8
0x40c49f…2af0
2 touches
0 conflicts
0x3d3ff127…95a0
0x40c49f…2af0
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 0x9a3068dd84…9918f0
Audit this contract →
← previous block·next block →recent activity