← previous blocknext block →recent activity
Analyzing
Block #96,280,110
5 transactions · 5 stateful · 2026-08-15 18:53:40 UTC
Parallelism
60/100
Blocked
20%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,280,110 · 5 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
1w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x486390bd…6bb9
0x065c9d…c394
4 touches
1 conflict
0x5b367d34…cc6e
0x065c9d…c394
3 touches
1 conflict
0x8058e752…f6f6
0x065c9d…c394
3 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x018c6250…3a44
0x065c9d…c394
2 touches
0 conflicts
0x06e40499…165e
0x2b46c0…1669
2 touches
0 conflicts
0x45f562b2…9294
0x2b46c0…1669
2 touches
0 conflicts
0x8488f10f…9353
0x2b46c0…1669
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 0x486390bdbb…0d6bb9
Audit this contract →
← previous block·next block →recent activity