← previous blocknext block →recent activity
Analyzing
Block #86,964,933
19 transactions · 17 stateful · 2026-07-11 02:33:21 UTC
Parallelism
79/100
Blocked
24%
Avg conflicts / tx
0.47
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,964,933 · 19 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
6w07w19w210w311w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0xb652c396…b8fa
0x34b655…2a6f
6 touches
3 conflicts
0x1adc709e…d1ca
0x34b655…2a6f
4 touches
1 conflict
0x36890fff…f3d1
0x34b655…2a6f
4 touches
1 conflict
0x40883ce5…2ae2
0x34b655…2a6f
4 touches
1 conflict
0x45877cba…0b50
0x34b655…2a6f
4 touches
1 conflict
0x63546690…2c97
0x34b655…2a6f
4 touches
1 conflict
0x7734fae8…226e
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
6 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity