← previous blocknext block →recent activity
Analyzing
Block #102,493,517
32 transactions · 24 stateful · 2026-09-06 14:32:55 UTC
Parallelism
88/100
Blocked
42%
Avg conflicts / tx
0.47
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #102,493,517 · 32 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w26w07w111w313w116w017w122w023w124w026w327w130w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xb686e6f5…f6d1
0xc8689a…ee79
6 touches
3 conflicts
0xaad6be10…0801
0x2a68ba…90c5
6 touches
3 conflicts
0x06e40499…165e
0x34ae4d…3fc5
6 touches
3 conflicts
0x45f562b2…9294
0x34ae4d…3fc5
6 touches
3 conflicts
0x0d622e34…0000
0x681e90…ae09
6 touches
3 conflicts
0x8488f10f…9353
0x34ae4d…3fc5
6 touches
3 conflicts
0x8488f10f…9354
0x34ae4d…3fc5
6 touches
3 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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity