← previous blocknext block →recent activity
Analyzing
Block #100,859,038
22 transactions · 19 stateful · 2026-08-31 21:07:09 UTC
Parallelism
73/100
Blocked
68%
Avg conflicts / tx
1.18
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,859,038 · 22 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
1w02w13w24w35w37w49w210w312w414w116w519w321w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0aaf23b7…7139
0xd32edf…ff58
11 touches
15 conflicts
0x2bbc0cfb…c2bf
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x5f77d607…2c84
0x065c9d…c394
6 touches
3 conflicts
0x00000000…001c
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 0x0aaf23b7f5…027139
Audit this contract →
← previous block·next block →recent activity