← previous blocknext block →recent activity
Analyzing
Block #101,300,261
19 transactions · 15 stateful · 2026-09-02 10:07:10 UTC
Parallelism
68/100
Blocked
67%
Avg conflicts / tx
1.21
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #101,300,261 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w06w18w311w312w414w515w116w418w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x36784a83…6479
0xd32edf…ff58
11 touches
15 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001c
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002c
0x1b6862…e19c
6 touches
3 conflicts
0x2bbc0cfb…c2bf
0x1b6862…e19c
6 touches
3 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
15 conflicts on slot 0x36784a836a…c86479
Audit this contract →
← previous block·next block →recent activity