← previous blocknext block →recent activity
Analyzing
Block #97,532,309
21 transactions · 21 stateful · 2026-08-20 04:37:42 UTC
Parallelism
76/100
Blocked
57%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,532,309 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w05w16w07w18w19w211w212w213w315w316w417w419w320w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0x16a8cd0c…27bd
0x34b655…2a6f
8 touches
6 conflicts
0x49cbdb1b…bda4
0x065c9d…c394
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0x2df2964f…78a1
0x34b655…2a6f
6 touches
3 conflicts
0x105cfb90…c9b9
0x065c9d…c394
5 touches
3 conflicts
0x2faeb77a…58f6
0x34b655…2a6f
4 touches
1 conflict
0xa8e3ccb9…86d8
0x34b655…2a6f
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
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity