← previous blocknext block →recent activity
Analyzing
Block #94,670,030
20 transactions · 20 stateful · 2026-08-10 03:37:47 UTC
Parallelism
55/100
Blocked
60%
Avg conflicts / tx
2.35
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #94,670,030 · 20 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w05w16w28w312w413w514w615w716w217w319w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xac2a0273…721b
0x34b655…2a6f
18 touches
36 conflicts
0x737acb78…fce8
0x34b655…2a6f
16 touches
28 conflicts
0x5502e1cc…3910
0x34b655…2a6f
12 touches
15 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0xc0a0f8b7…9c52
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x103be197…826c
0xa6afd3…d132
8 touches
6 conflicts
0x66a11a3b…0ee9
0xa6afd3…d132
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
36 conflicts on slot 0xac2a02739b…81721b
Audit this contract →
← previous block·next block →recent activity