← previous blocknext block →recent activity
Analyzing
Block #97,535,330
25 transactions · 25 stateful · 2026-08-20 04:52:53 UTC
Parallelism
84/100
Blocked
44%
Avg conflicts / tx
0.64
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,535,330 · 25 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w06w17w28w09w010w111w012w113w014w215w317w218w321w124w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x49cbdb1b…bda4
0x065c9d…c394
6 touches
3 conflicts
0x9f48add0…e017
0x065c9d…c394
5 touches
3 conflicts
0x5778d110…d2e6
0xc8689a…ee79
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x18865c9d…8ced
0xa6afd3…d132
4 touches
1 conflict
0x00000000…0007
0xc1570a…c91b
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: Kuru Exchange: Market-MON/USDC
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity