← previous blocknext block →recent activity
Analyzing
Block #102,479,430
39 transactions · 32 stateful · 2026-09-06 13:21:24 UTC
Parallelism
85/100
Blocked
47%
Avg conflicts / tx
0.67
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #102,479,430 · 39 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w17w08w19w010w112w013w114w215w017w219w120w021w022w123w024w127w128w331w432w535w036w137w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x5f77d607…2c84
0x065c9d…c394
6 touches
3 conflicts
0x892daf6e…48d8
0x065c9d…c394
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x3f1b6ec4…f2fb
0xd32edf…ff58
5 touches
3 conflicts
0x32e1d03e…68a7
0x34b655…2a6f
4 touches
1 conflict
0x3d13406e…eff1
0x34b655…2a6f
4 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
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity