← previous blocknext block →recent activity
Analyzing
Block #86,691,421
9 transactions · 8 stateful · 2026-07-09 20:05:31 UTC
Parallelism
78/100
Blocked
25%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,691,421 · 9 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
1w02w13w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4d4389b2…6e07
0x34b655…2a6f
4 touches
1 conflict
0x5b17482f…0dc4
0x34b655…2a6f
4 touches
1 conflict
0x3ba014e3…35d5
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x1dddd7ef…8f05
0x34b655…2a6f
2 touches
0 conflicts
0x2f28f5d5…fe07
0x34b655…2a6f
2 touches
0 conflicts
0x35b89cd8…5092
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
1 conflict on slot 0x4d4389b20d…b56e07
Audit this contract →
← previous block·next block →recent activity