← previous blocknext block →recent activity
Analyzing
Block #100,246,557
20 transactions · 15 stateful · 2026-08-29 17:42:19 UTC
Parallelism
65/100
Blocked
60%
Avg conflicts / tx
0.95
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,246,557 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w47w512w214w315w016w619w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0035ac3d…a0f4
0xd32edf…ff58
9 touches
10 conflicts
0x5f77d607…2c84
0x065c9d…c394
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…001f
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002f
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
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
10 conflicts on slot 0x0035ac3d6a…4fa0f4
Audit this contract →
← previous block·next block →recent activity