← previous blocknext block →recent activity
Analyzing
Block #97,556,192
22 transactions · 19 stateful · 2026-08-20 06:38:36 UTC
Parallelism
73/100
Blocked
47%
Avg conflicts / tx
0.64
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #97,556,192 · 22 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w05w17w08w09w214w315w116w419w420w521w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x246e5638…b635
0x34b655…2a6f
6 touches
3 conflicts
0x25ff7717…d4af
0x34b655…2a6f
6 touches
3 conflicts
0x0099420d…37b4
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…002a
0x1b6862…e19c
4 touches
1 conflict
0xba5743c7…21c1
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
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
3 conflicts on slot 0x246e5638a2…07b635
Audit this contract →
← previous block·next block →recent activity