← previous blocknext block →recent activity
Analyzing
Block #97,897,063
104 transactions · 60 stateful · 2026-08-21 11:34:44 UTC
Parallelism
86/100
Blocked
72%
Avg conflicts / tx
1.37
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #97,897,063 · 104 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
1w02w13w24w312w013w014w115w419w026w028w029w130w031w132w237w341w442w561w164w275w276w379w194w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0x103de0…bb55
20 touches
45 conflicts
0xca841faa…486a
0x34b655…2a6f
14 touches
21 conflicts
0x889d5e90…929a
0x2a68ba…90c5
12 touches
15 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x88c25490…e376
0x34b655…2a6f
10 touches
10 conflicts
0xbde524f4…43bf
0x34b655…2a6f
10 touches
10 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
10 touches
10 conflicts
0x5778d110…d2e6
0xc8689a…ee79
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: 0x103de0b5…25bb55
45 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity