← previous blocknext block →recent activity
Analyzing
Block #97,520,969
13 transactions · 12 stateful · 2026-08-20 03:40:39 UTC
Parallelism
85/100
Blocked
8%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #97,520,969 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49cbdb1b…bda4
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x947ad002…f68f
0x065c9d…c394
3 touches
1 conflict
0x771d7e9b…88c5
0x065c9d…c394
3 touches
1 conflict
0x8cf55475…8383
0x065c9d…c394
2 touches
0 conflicts
0x8d566979…b4e8
0x065c9d…c394
2 touches
0 conflicts
0xb0070c77…6cb3
0x065c9d…c394
2 touches
0 conflicts
0xc6c3d602…4771
0x065c9d…c394
2 touches
0 conflicts
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
1 conflict on slot 0x49cbdb1b43…f7bda4
Audit this contract →
← previous block·next block →recent activity