← previous blocknext block →recent activity
Analyzing
Block #86,849,223
22 transactions · 20 stateful · 2026-07-10 13:39:48 UTC
Parallelism
77/100
Blocked
55%
Avg conflicts / tx
1.27
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,849,223 · 22 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
1w02w13w04w15w26w37w410w011w112w213w215w316w420w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
10 touches
10 conflicts
0x03fb27fd…0c06
0x34b655…2a6f
8 touches
6 conflicts
0x0733be30…112f
0x34b655…2a6f
8 touches
6 conflicts
0x0e9a70ab…e67c
0x34b655…2a6f
8 touches
6 conflicts
0x22bc4ea4…5c8a
0x34b655…2a6f
8 touches
6 conflicts
0x922c7ebd…6600
0xc8689a…ee79
8 touches
6 conflicts
0x3d4584df…ffed
0x34b655…2a6f
8 touches
6 conflicts
0x588da1c1…6ae5
0x34b655…2a6f
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
10 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity