← previous blocknext block →recent activity
Analyzing
Block #100,126,520
11 transactions · 10 stateful · 2026-08-29 07:37:20 UTC
Parallelism
73/100
Blocked
30%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,126,520 · 11 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
2w03w06w17w18w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x348fda08…7e96
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xba38536d…2b7d
0x065c9d…c394
4 touches
1 conflict
0xb9868b52…c77f
0x34b655…2a6f
4 touches
1 conflict
0x45f562b2…9294
0x2b46c0…1669
2 touches
0 conflicts
0x8488f10f…9353
0x2b46c0…1669
2 touches
0 conflicts
0x8488f10f…9354
0x2b46c0…1669
2 touches
0 conflicts
0xc20bd100…8b0e
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
3 conflicts on slot 0x348fda08cf…fc7e96
Audit this contract →
← previous block·next block →recent activity