← previous blocknext block →recent activity
Analyzing
Block #106,469,333
35 transactions · 21 stateful · 2026-09-20 12:59:10 UTC
Parallelism
80/100
Blocked
57%
Avg conflicts / tx
0.6
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #106,469,333 · 35 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w48w510w615w016w317w118w219w325w532w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf02640ab…c11e
0xd32edf…ff58
9 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0xe783dfa4…5497
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0002
0xf5b5f7…6d70
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001c
0x1b6862…e19c
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: FastLane: FastLaneAuctionHandler
10 conflicts on slot 0xf02640ab4d…c9c11e
Audit this contract →
← previous block·next block →recent activity