← previous blocknext block →recent activity
Analyzing
Block #97,527,460
20 transactions · 18 stateful · 2026-08-20 04:13:18 UTC
Parallelism
85/100
Blocked
44%
Avg conflicts / tx
0.65
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #97,527,460 · 20 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
4w05w16w27w08w19w011w012w113w215w116w218w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x002fed35…79fa
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x00000000…0002
0x103de0…bb55
6 touches
3 conflicts
0x71cb7120…d291
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x49cbdb1b…bda4
0x065c9d…c394
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
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: MarginAccount
3 conflicts on slot 0x002fed350f…7379fa
Audit this contract →
← previous block·next block →recent activity