← previous blocknext block →recent activity
Analyzing
Block #97,530,924
50 transactions · 43 stateful · 2026-08-20 04:30:44 UTC
Parallelism
66/100
Blocked
74%
Avg conflicts / tx
2.78
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #97,530,924 · 50 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
1w02w13w24w36w013w014w120w223w624w426w731w1032w1135w236w337w438w443w849w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xec7d120d…7084
0x34b655…2a6f
16 touches
28 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x2dcc0868…26bf
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x17a7f697…dcb2
0x1b6862…e19c
10 touches
10 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 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 0xec7d120df9…5d7084
Audit this contract →
← previous block·next block →recent activity