← previous blocknext block →recent activity
Analyzing
Block #100,625,738
36 transactions · 28 stateful · 2026-08-31 01:33:10 UTC
Parallelism
78/100
Blocked
61%
Avg conflicts / tx
1.56
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #100,625,738 · 36 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w25w011w312w414w118w519w620w721w132w433w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x69f963df…0dbf
0xd32edf…ff58
15 touches
28 conflicts
0x00000000…0012
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0013
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…0015
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…001f
0x1b6862…e19c
14 touches
21 conflicts
0x00000000…002f
0x1b6862…e19c
14 touches
21 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
14 touches
21 conflicts
0x98067f20…59ea
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 0x69f963dfea…b30dbf
Audit this contract →
← previous block·next block →recent activity