← previous blocknext block →recent activity
Analyzing
Block #88,086,333
13 transactions · 13 stateful · 2026-07-16 07:33:22 UTC
Parallelism
85/100
Blocked
23%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #88,086,333 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w07w18w19w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0352ac09…8b3d
0x34b655…2a6f
4 touches
1 conflict
0x08cf1b01…68e8
0x34b655…2a6f
4 touches
1 conflict
0x08cf1b01…68e9
0x34b655…2a6f
4 touches
1 conflict
0x21280422…0930
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x48b13e5e…3c2a
0x34b655…2a6f
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
1 conflict on slot 0x0352ac09c5…7f8b3d
Audit this contract →
← previous block·next block →recent activity