← previous blocknext block →recent activity
Analyzing
Block #86,690,628
24 transactions · 18 stateful · 2026-07-09 20:00:15 UTC
Parallelism
83/100
Blocked
28%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,690,628 · 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
4w05w111w012w213w014w122w223w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x93701943…012b
0x34b655…2a6f
6 touches
3 conflicts
0xf5042875…9a93
0x34b655…2a6f
6 touches
3 conflicts
0x1535d171…c68b
0x34b655…2a6f
6 touches
3 conflicts
0x1b374c44…96d9
0x34b655…2a6f
6 touches
3 conflicts
0x56b5f5c0…a3ad
0x34b655…2a6f
4 touches
1 conflict
0x666b28db…11f0
0x34b655…2a6f
4 touches
1 conflict
0x6e3bb84c…2d7f
0x34b655…2a6f
4 touches
1 conflict
0x7f5b2c1d…0e7f
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 0x937019434b…d8012b
Audit this contract →
← previous block·next block →recent activity