← previous blocknext block →recent activity
Analyzing
Block #97,673,956
53 transactions · 48 stateful · 2026-08-20 16:40:17 UTC
Parallelism
68/100
Blocked
77%
Avg conflicts / tx
3.23
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #97,673,956 · 53 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
1w02w15w26w37w49w010w111w012w113w215w317w419w521w623w434w235w536w338w645w948w1250w1451w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
24 touches
66 conflicts
0xac2a0273…721b
0x34b655…2a6f
14 touches
21 conflicts
0x737acb78…fce8
0x34b655…2a6f
12 touches
15 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
12 touches
15 conflicts
0xec7d120d…7084
0x34b655…2a6f
12 touches
15 conflicts
0x157b6348…8604
0x34b655…2a6f
12 touches
15 conflicts
0x92385428…6941
0x34b655…2a6f
12 touches
15 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
12 touches
15 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