← previous blocknext block →recent activity
Analyzing
Block #100,599,944
136 transactions · 69 stateful · 2026-08-30 23:23:24 UTC
Parallelism
87/100
Blocked
81%
Avg conflicts / tx
2.28
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #100,599,944 · 136 txs across 18 waves · depth 18
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w49w459w160w262w363w564w666w669w770w876w781w982w1083w1184w1285w1386w1487w1592w1693w994w10120w17
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x665a3f4f…1038
0xd32edf…ff58
33 touches
136 conflicts
0x17606ba6…1b6e
0x754704…b603
20 touches
45 conflicts
0x00000000…0013
0x1b6862…e19c
20 touches
45 conflicts
0x00000000…0015
0x1b6862…e19c
20 touches
45 conflicts
0x1f8a126c…9aa7
0x1b6862…e19c
20 touches
45 conflicts
0x889d5e90…929a
0x2a68ba…90c5
20 touches
45 conflicts
0x00000000…002e
0x1b6862…e19c
18 touches
36 conflicts
0x00000000…0012
0x1b6862…e19c
18 touches
36 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
136 conflicts on slot 0x665a3f4f2a…0d1038
Audit this contract →
← previous block·next block →recent activity