← previous blocknext block →recent activity
Analyzing
Block #86,048,067
24 transactions · 21 stateful · 2026-07-06 20:25:44 UTC
Parallelism
75/100
Blocked
43%
Avg conflicts / tx
0.79
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,048,067 · 24 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w15w09w010w113w114w015w117w018w119w220w321w422w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x63c900f4…2600
0x34b655…2a6f
6 touches
3 conflicts
0xa153042c…c754
0x34b655…2a6f
6 touches
3 conflicts
0xa51de3df…c65a
0x34b655…2a6f
6 touches
3 conflicts
0xd5aa8069…a135
0x34b655…2a6f
6 touches
3 conflicts
0xd99b3b64…1c95
0x34b655…2a6f
6 touches
3 conflicts
0x65903ef9…2567
0x34b655…2a6f
6 touches
3 conflicts
0x4546ebad…b908
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
15 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity