← previous blocknext block →recent activity
Analyzing
Block #100,140,710
20 transactions · 14 stateful · 2026-08-29 08:48:54 UTC
Parallelism
85/100
Blocked
14%
Avg conflicts / tx
0.15
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #100,140,710 · 20 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
2w016w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x443a3e47…f4a4
0x065c9d…c394
6 touches
3 conflicts
0xfcb7b8b2…ebb3
0x065c9d…c394
4 touches
1 conflict
0x4fb38227…7ee3
0x065c9d…c394
3 touches
1 conflict
0xad388df1…76f1
0x065c9d…c394
3 touches
1 conflict
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity