← previous blocknext block →recent activity
Analyzing
Block #100,601,305
130 transactions · 63 stateful · 2026-08-30 23:30:15 UTC
Parallelism
84/100
Blocked
83%
Avg conflicts / tx
2.55
Longest chain
21 deep
Execution timeline
did this block parallelize well?
view
block #100,601,305 · 130 txs across 21 waves · depth 21
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
wave w18
wave w19
wave w20
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w812w987w1088w1189w1290w1391w1494w15103w16104w17105w18108w19110w20
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x91dc4f79…8e37
0xd32edf…ff58
41 touches
210 conflicts
0x00000000…0013
0x1b6862…e19c
20 touches
45 conflicts
0x00000000…0015
0x1b6862…e19c
20 touches
45 conflicts
0x00000000…001e
0x1b6862…e19c
20 touches
45 conflicts
0x00000000…002e
0x1b6862…e19c
20 touches
45 conflicts
0x5a3732cb…edb2
0x1b6862…e19c
20 touches
45 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
20 touches
45 conflicts
0x00000000…0012
0x1b6862…e19c
20 touches
45 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
210 conflicts on slot 0x91dc4f792b…a68e37
Audit this contract →
← previous block·next block →recent activity