← previous blocknext block →recent activity
Analyzing
Block #97,559,620
14 transactions · 11 stateful · 2026-08-20 06:56:06 UTC
Parallelism
86/100
Blocked
18%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #97,559,620 · 14 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
1w02w03w15w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0xc28d4c07…fdc7
0x065c9d…c394
4 touches
1 conflict
0xeaf2b453…310b
0x065c9d…c394
3 touches
1 conflict
0x25e9036b…f497
0x065c9d…c394
3 touches
1 conflict
0xb6df4681…684a
0x065c9d…c394
3 touches
1 conflict
0xeb57e0bd…f4d5
0x065c9d…c394
3 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity