← previous blocknext block →recent activity
Analyzing
Block #97,523,844
15 transactions · 13 stateful · 2026-08-20 03:55:07 UTC
Parallelism
80/100
Blocked
31%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #97,523,844 · 15 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w07w19w110w214w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x49cbdb1b…bda4
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xee4fe1f7…3ead
0x34b655…2a6f
4 touches
1 conflict
0x27a04273…27c5
0x065c9d…c394
4 touches
1 conflict
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0x6a0d1e16…8182
0x065c9d…c394
4 touches
1 conflict
0xddb8ed74…894a
0x065c9d…c394
3 touches
1 conflict
0x5ac73b06…d405
0x065c9d…c394
3 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 0x49cbdb1b43…f7bda4
Audit this contract →
← previous block·next block →recent activity