← previous blocknext block →recent activity
Analyzing
Block #86,665,307
20 transactions · 19 stateful · 2026-07-09 17:11:13 UTC
Parallelism
75/100
Blocked
53%
Avg conflicts / tx
0.95
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,665,307 · 20 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
1w02w13w24w35w47w08w19w010w216w117w218w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0e9a70ab…e67c
0x34b655…2a6f
8 touches
6 conflicts
0x1951ee47…540f
0x34b655…2a6f
8 touches
6 conflicts
0x3d4584df…ffed
0x34b655…2a6f
8 touches
6 conflicts
0x9138a113…0d5f
0x34b655…2a6f
8 touches
6 conflicts
0x9ad66bbf…929c
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xfaef08b1…0696
0x34b655…2a6f
8 touches
6 conflicts
0x922c7ebd…6600
0xc8689a…ee79
8 touches
6 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
6 conflicts on slot 0x0e9a70abf6…d0e67c
Audit this contract →
← previous block·next block →recent activity