← previous blocknext block →recent activity
Analyzing
Block #101,065,421
22 transactions · 21 stateful · 2026-09-01 14:25:29 UTC
Parallelism
64/100
Blocked
67%
Avg conflicts / tx
1.82
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #101,065,421 · 22 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w47w58w113w320w621w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc4f93b14…68fc
0xd32edf…ff58
15 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0018
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0028
0x1b6862…e19c
8 touches
6 conflicts
0x6b1259e6…4e0d
0x1b6862…e19c
8 touches
6 conflicts
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
28 conflicts on slot 0xc4f93b1487…3e68fc
Audit this contract →
← previous block·next block →recent activity