← previous blocknext block →recent activity
Analyzing
Block #97,384,455
65 transactions · 55 stateful · 2026-08-19 15:54:18 UTC
Parallelism
77/100
Blocked
64%
Avg conflicts / tx
2.14
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #97,384,455 · 65 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w16w29w011w112w113w214w315w217w418w223w427w128w231w632w736w939w1040w241w242w343w4
- 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
0xc824469a…6425
0x34b655…2a6f
16 touches
28 conflicts
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0xbdcff57a…6ea3
0x34b655…2a6f
12 touches
15 conflicts
0xe8aab7db…a319
0xa6afd3…d132
10 touches
10 conflicts
0x3741a573…e309
0x34b655…2a6f
10 touches
10 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
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
36 conflicts on slot 0xac2a02739b…81721b
Audit this contract →
← previous block·next block →recent activity