← previous blocknext block →recent activity
Analyzing
Block #86,701,613
12 transactions · 9 stateful · 2026-07-09 21:13:32 UTC
Parallelism
58/100
Blocked
44%
Avg conflicts / tx
0.58
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,701,613 · 12 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w27w38w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00958d6e…1d09
0x34b655…2a6f
6 touches
3 conflicts
0x00958d6e…1d0a
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x78c30d78…2c38
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0x97884f85…7818
0x34b655…2a6f
6 touches
3 conflicts
0xa523c16d…15cd
0x34b655…2a6f
6 touches
3 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 0x00958d6e36…b71d09
Audit this contract →
← previous block·next block →recent activity