← previous blocknext block →recent activity
Analyzing
Block #86,963,471
25 transactions · 24 stateful · 2026-07-11 02:23:34 UTC
Parallelism
68/100
Blocked
38%
Avg conflicts / tx
0.8
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #86,963,471 · 25 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w29w310w411w512w613w717w018w023w124w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0733be30…112f
0x34b655…2a6f
10 touches
10 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
10 touches
10 conflicts
0x32f1fe90…5ee3
0x34b655…2a6f
8 touches
6 conflicts
0x8a35acfb…d1ad
0xb1dbf0…c0d3
6 touches
3 conflicts
0x7e5ea60a…c4ab
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xd708bac6…2e5d
0x34b655…2a6f
6 touches
3 conflicts
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 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
10 conflicts on slot 0x0733be30d6…38112f
Audit this contract →
← previous block·next block →recent activity