← previous blocknext block →recent activity
Analyzing
Block #104,159,833
26 transactions · 24 stateful · 2026-09-12 10:47:40 UTC
Parallelism
65/100
Blocked
67%
Avg conflicts / tx
1.46
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #104,159,833 · 26 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w511w515w616w717w419w422w825w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcc7b61c9…a260
0xd32edf…ff58
13 touches
21 conflicts
0xaad6be10…0801
0x2a68ba…90c5
10 touches
10 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…001e
0x1b6862…e19c
6 touches
3 conflicts
0xba5743c7…21c5
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002e
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
21 conflicts on slot 0xcc7b61c9fc…71a260
Audit this contract →
← previous block·next block →recent activity