← previous blocknext block →recent activity
Analyzing
Block #97,557,638
25 transactions · 19 stateful · 2026-08-20 06:45:57 UTC
Parallelism
88/100
Blocked
32%
Avg conflicts / tx
0.28
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #97,557,638 · 25 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w06w09w010w111w115w116w221w124w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc76e6407…2808
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0xac2a0273…7212
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x1e0cf9b1…e924
0x40c49f…2af0
4 touches
1 conflict
0x655aa1bb…138c
0x40c49f…2af0
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x4d953953…ac1f
0xa6afd3…d132
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 0xc76e6407c8…062808
Audit this contract →
← previous block·next block →recent activity