← previous blocknext block →recent activity
Analyzing
Block #97,561,296
78 transactions · 65 stateful · 2026-08-20 07:04:40 UTC
Parallelism
78/100
Blocked
66%
Avg conflicts / tx
2.38
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #97,561,296 · 78 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
1w02w15w07w18w010w012w113w214w015w116w217w318w419w520w621w222w323w439w345w448w551w166w268w877w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
24 touches
66 conflicts
0x482471ad…122f
0x34b655…2a6f
22 touches
55 conflicts
0xc824469a…6425
0x34b655…2a6f
20 touches
45 conflicts
0x889d5e90…929a
0x2a68ba…90c5
14 touches
21 conflicts
0x00000000…003d
0x40c49f…2af0
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0xc76e6407…2808
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0x851145…3f07
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity