← previous blocknext block →recent activity
Analyzing
Block #86,964,506
13 transactions · 12 stateful · 2026-07-11 02:30:29 UTC
Parallelism
62/100
Blocked
42%
Avg conflicts / tx
0.62
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,964,506 · 13 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w06w28w39w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0xa42e8482…b88f
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x11bb4e7c…bf16
0x34b655…2a6f
4 touches
1 conflict
0x18d21314…f582
0x34b655…2a6f
4 touches
1 conflict
0x1ca5e0a6…aabb
0x34b655…2a6f
4 touches
1 conflict
0x1e7927e5…282d
0x34b655…2a6f
4 touches
1 conflict
0x33875aea…a440
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 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity