← previous blocknext block →recent activity
Analyzing
Block #97,385,589
50 transactions · 40 stateful · 2026-08-19 16:02:25 UTC
Parallelism
64/100
Blocked
78%
Avg conflicts / tx
2.82
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #97,385,589 · 50 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
1w02w13w24w312w416w720w221w325w427w628w630w831w932w633w1043w1145w1348w1649w17
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x967ba723…6d0f
0x34b655…2a6f
16 touches
28 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
14 touches
21 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
14 touches
21 conflicts
0x00000000…002e
0x1b6862…e19c
12 touches
15 conflicts
0x10c19272…7445
0x1b6862…e19c
12 touches
15 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
12 touches
15 conflicts
0x737acb78…fce8
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
28 conflicts on slot 0x967ba7239d…2d6d0f
Audit this contract →
← previous block·next block →recent activity