← previous blocknext block →recent activity
Analyzing
Block #106,046,065
19 transactions · 14 stateful · 2026-09-19 01:28:53 UTC
Parallelism
84/100
Blocked
21%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #106,046,065 · 19 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
1w02w13w04w218w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x649614fd…06e9
0x065c9d…c394
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x9ba7d0c8…ec52
0xee8c0e…1242
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xcc8faac2…c766
0x065c9d…c394
4 touches
1 conflict
0x00000000…0000
0x354d92…66fb
4 touches
1 conflict
0x00000000…0001
0x354d92…66fb
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
3 conflicts on slot 0x649614fd3b…d906e9
Audit this contract →
← previous block·next block →recent activity