← previous blocknext block →recent activity
Analyzing
Block #86,484,601
30 transactions · 28 stateful · 2026-07-08 21:01:00 UTC
Parallelism
67/100
Blocked
57%
Avg conflicts / tx
1.8
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #86,484,601 · 30 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w05w17w210w011w112w113w114w215w316w417w518w619w720w824w326w728w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
16 touches
28 conflicts
0xdba422af…42ec
0x34b655…2a6f
10 touches
10 conflicts
0x6e334aa4…583b
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xc948dbdc…199a
0x34b655…2a6f
8 touches
6 conflicts
0x3f24a374…6bc3
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…001c
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002c
0x1b6862…e19c
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
28 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity