← previous blocknext block →recent activity
Analyzing
Block #101,666,491
25 transactions · 20 stateful · 2026-09-03 16:49:48 UTC
Parallelism
60/100
Blocked
70%
Avg conflicts / tx
1.84
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #101,666,491 · 25 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w47w58w69w711w616w721w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x71cf8bd1…38a8
0xd32edf…ff58
15 touches
28 conflicts
0x00000000…0013
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0015
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…001c
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…002c
0x1b6862…e19c
14 touches
21 conflicts
0x0f28fb99…3d2d
0x1b6862…e19c
14 touches
21 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0012
0x1b6862…e19c
14 touches
21 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 0x71cf8bd1fb…c138a8
Audit this contract →
← previous block·next block →recent activity