← previous blocknext block →recent activity
Analyzing
Block #86,608,818
24 transactions · 18 stateful · 2026-07-09 10:52:41 UTC
Parallelism
83/100
Blocked
22%
Avg conflicts / tx
0.29
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,608,818 · 24 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
2w03w18w012w020w121w223w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1941b441…5889
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x11431f9d…42c5
0x34b655…2a6f
4 touches
1 conflict
0x20238614…e0be
0x34b655…2a6f
4 touches
1 conflict
0x31519d10…f76b
0x34b655…2a6f
4 touches
1 conflict
0x33eb5dfa…2338
0x34b655…2a6f
4 touches
1 conflict
0x342f88f5…2a06
0x34b655…2a6f
4 touches
1 conflict
0x574628e9…dcc3
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 0x1941b4413e…0c5889
Audit this contract →
← previous block·next block →recent activity