← previous blocknext block →recent activity
Analyzing
Block #86,694,397
20 transactions · 16 stateful · 2026-07-09 20:25:21 UTC
Parallelism
80/100
Blocked
31%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,694,397 · 20 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
3w05w06w19w210w312w013w117w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x4c7b72e8…9a1f
0x34b655…2a6f
6 touches
3 conflicts
0x0733be30…112f
0x34b655…2a6f
6 touches
3 conflicts
0x248e43aa…7287
0x34b655…2a6f
4 touches
1 conflict
0x2833ba3e…8b1e
0x34b655…2a6f
4 touches
1 conflict
0x296ff593…ecdb
0x34b655…2a6f
4 touches
1 conflict
0x6d597594…10d1
0x34b655…2a6f
4 touches
1 conflict
0x6d597594…10d2
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
3 conflicts on slot 0x7e5ea60ab2…b0c4aa
Audit this contract →
← previous block·next block →recent activity