← previous blocknext block →recent activity
Analyzing
Block #86,946,506
13 transactions · 11 stateful · 2026-07-11 00:30:10 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,946,506 · 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
4w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac3e4969…39e9
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x0db691ab…3ee3
0x34b655…2a6f
2 touches
0 conflicts
0x146f0fd7…34d3
0x34b655…2a6f
2 touches
0 conflicts
0x16515fff…b121
0x34b655…2a6f
2 touches
0 conflicts
0x1ba5d36c…9336
0x34b655…2a6f
2 touches
0 conflicts
0x1dd93d78…c255
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 0xac3e4969cf…1739e9
Audit this contract →
← previous block·next block →recent activity