← previous blocknext block →recent activity
Analyzing
Block #86,964,871
11 transactions · 9 stateful · 2026-07-11 02:32:56 UTC
Parallelism
64/100
Blocked
33%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,964,871 · 11 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
4w05w16w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x3a996b35…bc8f
0x34b655…2a6f
6 touches
3 conflicts
0xb652c396…b8fa
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xed4a0d72…065f
0x34b655…2a6f
6 touches
3 conflicts
0x41d7e149…baec
0x34b655…2a6f
4 touches
1 conflict
0x4234c12b…6919
0x34b655…2a6f
4 touches
1 conflict
0x595cbd16…dac4
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
6 conflicts on slot 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity