← previous blocknext block →recent activity
Analyzing
Block #97,546,292
67 transactions · 67 stateful · 2026-08-20 05:48:02 UTC
Parallelism
97/100
Blocked
3%
Avg conflicts / tx
0.03
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #97,546,292 · 67 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
1w02w05w166w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…0007
0xc1570a…c91b
4 touches
1 conflict
0xcc8faac2…c766
0x065c9d…c394
4 touches
1 conflict
0x5f387af5…e0f2
0x065c9d…c394
2 touches
0 conflicts
0x96ff3001…13d9
0x065c9d…c394
2 touches
0 conflicts
0xb25ea5b5…72d3
0x065c9d…c394
2 touches
0 conflicts
0xc91f570f…9d78
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
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