← previous blocknext block →recent activity
Analyzing
Block #100,141,112
32 transactions · 28 stateful · 2026-08-29 08:50:56 UTC
Parallelism
78/100
Blocked
71%
Avg conflicts / tx
1.63
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #100,141,112 · 32 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
1w02w14w25w36w48w59w521w622w423w525w326w429w631w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xaf634dd2…33e6
0xd32edf…ff58
13 touches
21 conflicts
0x00000000…0013
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0012
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…0015
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…001d
0x1b6862…e19c
12 touches
15 conflicts
0x00000000…002d
0x1b6862…e19c
12 touches
15 conflicts
0x2ce2d49e…d18a
0x1b6862…e19c
12 touches
15 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
12 touches
15 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 0xaf634dd20b…1733e6
Audit this contract →
← previous block·next block →recent activity