← previous blocknext block →recent activity
Analyzing
Block #97,364,625
22 transactions · 21 stateful · 2026-08-19 14:10:37 UTC
Parallelism
77/100
Blocked
48%
Avg conflicts / tx
1.14
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,364,625 · 22 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w38w010w411w012w113w214w315w419w020w121w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x65d2bd64…8afc
0x34b655…2a6f
10 touches
10 conflicts
0x654081b4…b1f8
0xd32edf…ff58
9 touches
10 conflicts
0x70cfbacf…5c46
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…001e
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002e
0x1b6862…e19c
6 touches
3 conflicts
0x59658b83…222b
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 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
10 conflicts on slot 0x65d2bd6411…dc8afc
Audit this contract →
← previous block·next block →recent activity