← previous blocknext block →recent activity
Analyzing
Block #97,601,938
50 transactions · 40 stateful · 2026-08-20 10:30:25 UTC
Parallelism
66/100
Blocked
78%
Avg conflicts / tx
2.2
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #97,601,938 · 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
1w02w14w05w112w215w316w417w518w320w021w122w123w124w225w327w436w337w641w443w1045w1246w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
18 touches
36 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
14 touches
21 conflicts
0x69352f9f…5449
0x34b655…2a6f
12 touches
15 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x92385428…6941
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
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
36 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity