← previous blocknext block →recent activity
Analyzing
Block #84,498,608
14 transactions · 12 stateful · 2026-06-29 16:16:24 UTC
Parallelism
64/100
Blocked
33%
Avg conflicts / tx
0.36
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,498,608 · 14 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w111w212w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xd29e547b…a1dd
0x34b655…2a6f
4 touches
1 conflict
0xa16b3e4e…0787
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xf07d9867…2335
0x34b655…2a6f
4 touches
1 conflict
0xa16b3e4e…0786
0x34b655…2a6f
4 touches
1 conflict
0xec85756f…0ba2
0x34b655…2a6f
4 touches
1 conflict
0x79eac3ad…cedc
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
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity