← previous blocknext block →recent activity
Analyzing
Block #86,688,346
11 transactions · 8 stateful · 2026-07-09 19:45:02 UTC
Parallelism
82/100
Blocked
13%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,688,346 · 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
2w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x56b5f5c0…a3ad
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x02c4bb0f…f2c8
0x34b655…2a6f
2 touches
0 conflicts
0x078f6b71…af4e
0x34b655…2a6f
2 touches
0 conflicts
0x1a7d77fe…f01a
0x34b655…2a6f
2 touches
0 conflicts
0x20bfcb14…4fd0
0x34b655…2a6f
2 touches
0 conflicts
0x352852e1…e791
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 0x56b5f5c03e…07a3ad
Audit this contract →
← previous block·next block →recent activity