← previous blocknext block →recent activity
Analyzing
Block #97,535,745
20 transactions · 17 stateful · 2026-08-20 04:54:59 UTC
Parallelism
80/100
Blocked
35%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,535,745 · 20 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
2w03w04w15w06w011w012w213w114w316w119w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc372b48d…7dc5
0x065c9d…c394
7 touches
6 conflicts
0x002fed35…79fa
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0xdb392027…0308
0x34b655…2a6f
4 touches
1 conflict
0xdb392027…0309
0x34b655…2a6f
4 touches
1 conflict
0x8e485ef0…8a8a
0x3bd359…433a
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x00000000…003d
0x851145…3f07
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 0xc372b48d39…697dc5
Audit this contract →
← previous block·next block →recent activity