← previous blocknext block →recent activity
Analyzing
Block #105,855,906
21 transactions · 20 stateful · 2026-09-18 09:30:48 UTC
Parallelism
86/100
Blocked
35%
Avg conflicts / tx
0.48
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #105,855,906 · 21 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
2w05w06w07w18w212w113w214w116w017w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xd17580f9…ece1
0x754704…b603
6 touches
3 conflicts
0x00000000…0002
0xf5b5f7…6d70
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x1eea6462…cbc7
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x49cbdb1b…bda4
0x065c9d…c394
4 touches
1 conflict
0x1269e668…aed5
0x065c9d…c394
3 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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity