← previous blocknext block →recent activity
Analyzing
Block #97,552,750
51 transactions · 46 stateful · 2026-08-20 06:20:59 UTC
Parallelism
65/100
Blocked
83%
Avg conflicts / tx
2.98
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #97,552,750 · 51 txs across 18 waves · depth 18
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
wave w17
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w412w115w316w418w519w222w325w526w627w728w830w531w533w942w1043w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0x0304ed8a…9f25
0x34b655…2a6f
16 touches
28 conflicts
0x00000000…003d
0xa6afd3…d132
14 touches
21 conflicts
0x22414fbb…1edf
0xa6afd3…d132
14 touches
21 conflicts
0xac2a0273…721b
0x34b655…2a6f
12 touches
15 conflicts
0x737acb78…fce8
0x34b655…2a6f
12 touches
15 conflicts
0xe2457683…1957
0xa6afd3…d132
12 touches
15 conflicts
0x889d5e90…929a
0x2a68ba…90c5
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
28 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity