← previous blocknext block →recent activity
Analyzing
Block #97,518,305
38 transactions · 34 stateful · 2026-08-20 03:27:15 UTC
Parallelism
55/100
Blocked
68%
Avg conflicts / tx
3.11
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #97,518,305 · 38 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
1w03w04w16w07w18w19w211w012w313w415w416w517w118w230w1032w1233w1337w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
24 touches
66 conflicts
0x5caf9f43…a348
0x34b655…2a6f
14 touches
21 conflicts
0xac2a0273…721b
0x34b655…2a6f
14 touches
21 conflicts
0x737acb78…fce8
0x34b655…2a6f
10 touches
10 conflicts
0x95f0b212…5f7a
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xe5e7089a…fb91
0x34b655…2a6f
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
66 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity