← previous blocknext block →recent activity
Analyzing
Block #94,807,319
48 transactions · 41 stateful · 2026-08-10 15:09:48 UTC
Parallelism
65/100
Blocked
73%
Avg conflicts / tx
2.6
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #94,807,319 · 48 txs across 17 waves · depth 17
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
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w16w27w38w010w111w213w315w416w517w618w719w820w921w1028w133w338w439w543w1246w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xec7d120d…7084
0x34b655…2a6f
22 touches
55 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0xf0d45ffd…89cf
0x34b655…2a6f
12 touches
15 conflicts
0xac2a0273…721b
0x34b655…2a6f
10 touches
10 conflicts
0x95c47f03…f1bb
0x34b655…2a6f
10 touches
10 conflicts
0x737acb78…fce8
0x34b655…2a6f
10 touches
10 conflicts
0x989252a1…d812
0xa6afd3…d132
8 touches
6 conflicts
0x00000000…003d
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
55 conflicts on slot 0xec7d120df9…5d7084
Audit this contract →
← previous block·next block →recent activity