← previous blocknext block →recent activity
Analyzing
Block #97,517,988
16 transactions · 15 stateful · 2026-08-20 03:25:39 UTC
Parallelism
69/100
Blocked
33%
Avg conflicts / tx
0.63
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #97,517,988 · 16 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
1w02w03w16w29w310w415w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x068dc9ff…7ff1
0x065c9d…c394
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
8 touches
6 conflicts
0x0778475b…bd75
0x2a68ba…90c5
8 touches
6 conflicts
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x8f478f26…9d56
0x000000…012a
2 touches
0 conflicts
0x9cafc3b6…ee8c
0x000000…012a
2 touches
0 conflicts
0x335a161d…fe7f
0x000000…012a
2 touches
0 conflicts
0x00000000…0000
0x16d564…365f
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
6 conflicts on slot 0x068dc9ffe9…4c7ff1
Audit this contract →
← previous block·next block →recent activity