← previous blocknext block →recent activity
Analyzing
Block #86,620,401
43 transactions · 34 stateful · 2026-07-09 12:10:01 UTC
Parallelism
63/100
Blocked
65%
Avg conflicts / tx
2.21
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #86,620,401 · 43 txs across 16 waves · depth 16
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w26w315w016w117w218w319w420w521w622w723w824w928w229w331w333w1037w1140w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
22 touches
55 conflicts
0x1941b441…5889
0x34b655…2a6f
12 touches
15 conflicts
0x5bb46f6c…7693
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xf806218e…c4da
0x34b655…2a6f
9 touches
10 conflicts
0x079a5590…cdbc
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x40c49f…2af0
8 touches
6 conflicts
0x7e5ea60a…c4aa
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
55 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity