← previous blocknext block →recent activity
Analyzing
Block #86,958,404
13 transactions · 11 stateful · 2026-07-11 01:49:40 UTC
Parallelism
85/100
Blocked
9%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #86,958,404 · 13 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
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc6d563ee…1268
0x34b655…2a6f
4 touches
1 conflict
0xf726e2e2…e561
0x34b655…2a6f
4 touches
1 conflict
0x26bcd08c…8b42
0x34b655…2a6f
4 touches
1 conflict
0xc6d563ee…1269
0x34b655…2a6f
4 touches
1 conflict
0x36a85feb…891b
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0xb76f7c01…c3a5
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
1 conflict on slot 0xc6d563eed7…511268
Audit this contract →
← previous block·next block →recent activity