← previous blocknext block →recent activity
Analyzing
Block #97,667,327
49 transactions · 45 stateful · 2026-08-20 16:06:03 UTC
Parallelism
61/100
Blocked
60%
Avg conflicts / tx
3.35
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #97,667,327 · 49 txs across 19 waves · depth 19
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
wave w18
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w05w16w27w38w49w410w518w619w720w722w823w939w1040w1142w1345w1546w1647w17
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
28 touches
91 conflicts
0x5c45ce93…9285
0x34b655…2a6f
12 touches
15 conflicts
0x737acb78…fce8
0x34b655…2a6f
12 touches
15 conflicts
0xac2a0273…721b
0x34b655…2a6f
12 touches
15 conflicts
0x40ac662f…df77
0x34b655…2a6f
12 touches
15 conflicts
0x02b4abec…397d
0x34b655…2a6f
12 touches
15 conflicts
0x92385428…6941
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
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
91 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity