← previous blocknext block →recent activity
Analyzing
Block #97,604,848
35 transactions · 31 stateful · 2026-08-20 10:45:03 UTC
Parallelism
54/100
Blocked
74%
Avg conflicts / tx
2.77
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #97,604,848 · 35 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
1w02w03w14w05w16w07w18w29w310w411w212w513w617w719w820w921w1022w123w1124w225w329w1234w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
24 touches
66 conflicts
0x482471ad…122f
0x34b655…2a6f
22 touches
55 conflicts
0xdc1951c6…a28c
0x34b655…2a6f
14 touches
21 conflicts
0x6d13cf1e…dfa2
0x34b655…2a6f
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x6612f77f…30a0
0x34b655…2a6f
8 touches
6 conflicts
0x737acb78…fce8
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
66 conflicts on slot 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity