← previous blocknext block →recent activity
Analyzing
Block #106,408,274
11 transactions · 10 stateful · 2026-09-20 07:51:48 UTC
Parallelism
82/100
Blocked
20%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #106,408,274 · 11 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w19w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x2366d36c…79d8
0x4de0d8…bfc3
4 touches
1 conflict
0x2366d36c…79dd
0x4de0d8…bfc3
4 touches
1 conflict
0x2366d36c…79e8
0x4de0d8…bfc3
4 touches
1 conflict
0x2366d36c…79ec
0x4de0d8…bfc3
4 touches
1 conflict
0x7e32f1e0…5612
0x4de0d8…bfc3
4 touches
1 conflict
0xe3abe489…ebf2
0x4de0d8…bfc3
4 touches
1 conflict
0xe3abe489…ebf3
0x4de0d8…bfc3
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
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity