← previous blocknext block →recent activity
Analyzing
Block #85,253,622
12 transactions · 12 stateful · 2026-07-03 04:11:45 UTC
Parallelism
67/100
Blocked
25%
Avg conflicts / tx
0.42
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,253,622 · 12 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
3w05w110w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x27f2c756…0ffc
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x022b49db…a477
0x34b655…2a6f
4 touches
1 conflict
0x40822796…f0e0
0x34b655…2a6f
4 touches
1 conflict
0xa23fe333…747b
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x52c63247…ce02
0x0c65a0…0852
2 touches
0 conflicts
0x4d96e4d0…2c67
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 0x27f2c75698…900ffc
Audit this contract →
← previous block·next block →recent activity