← previous blocknext block →recent activity
Analyzing
Block #86,513,725
11 transactions · 9 stateful · 2026-07-09 00:15:17 UTC
Parallelism
82/100
Blocked
22%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,513,725 · 11 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
1w03w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9138a113…0d5f
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x326a02b5…8dad
0x34b655…2a6f
4 touches
1 conflict
0x01c969a3…227b
0x34b655…2a6f
2 touches
0 conflicts
0x11933a45…1daa
0x34b655…2a6f
2 touches
0 conflicts
0x1c9ce70a…2fc6
0x34b655…2a6f
2 touches
0 conflicts
0x206d06f5…48d3
0x34b655…2a6f
2 touches
0 conflicts
0x21924cd6…4a8b
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 0x9138a113b1…c30d5f
Audit this contract →
← previous block·next block →recent activity