← previous blocknext block →recent activity
Analyzing
Block #106,046,810
19 transactions · 15 stateful · 2026-09-19 01:32:38 UTC
Parallelism
74/100
Blocked
40%
Avg conflicts / tx
0.47
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,046,810 · 19 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w310w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7f6e3141…e368
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x14d1bf0e…e09c
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x00000000…0002
0xf5b5f7…6d70
4 touches
1 conflict
0x18afcad8…27a1
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: FastLane: FastLaneAuctionHandler
6 conflicts on slot 0x7f6e31412a…d7e368
Audit this contract →
← previous block·next block →recent activity