← previous blocknext block →recent activity
Analyzing
Block #97,629,011
26 transactions · 19 stateful · 2026-08-20 12:47:12 UTC
Parallelism
85/100
Blocked
37%
Avg conflicts / tx
0.31
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #97,629,011 · 26 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
1w02w14w26w29w015w116w017w119w220w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x53a21ada…59bb
0x065c9d…c394
4 touches
1 conflict
0x919fb5ce…b5a0
0x065c9d…c394
4 touches
1 conflict
0xcc4f1f14…aa5f
0x065c9d…c394
4 touches
1 conflict
0xdfa159d0…1576
0x065c9d…c394
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0x7c403af1…31b1
0x3bd359…433a
4 touches
1 conflict
0x00000000…0004
0x65d862…09f4
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity