← previous blocknext block →recent activity
Analyzing
Block #102,151,540
66 transactions · 51 stateful · 2026-09-05 09:40:02 UTC
Parallelism
68/100
Blocked
67%
Avg conflicts / tx
3.94
Longest chain
21 deep
Execution timeline
did this block parallelize well?
view
block #102,151,540 · 66 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
1w02w13w24w35w46w57w68w79w810w911w1015w1119w1120w1221w1322w1423w1524w1625w1726w1848w1951w20
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x384d362c…60e3
0xd32edf…ff58
41 touches
210 conflicts
0x00000000…0015
0x1b6862…e19c
20 touches
45 conflicts
0x7d4f80a4…bb18
0x1b6862…e19c
20 touches
45 conflicts
0x00000000…0013
0x1b6862…e19c
20 touches
45 conflicts
0x00000000…0012
0x1b6862…e19c
18 touches
36 conflicts
0x00000000…001d
0x1b6862…e19c
18 touches
36 conflicts
0x00000000…002d
0x1b6862…e19c
18 touches
36 conflicts
0xd9f18d9a…141d
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
210 conflicts on slot 0x384d362c9b…1960e3
Audit this contract →
← previous block·next block →recent activity