← previous blocknext block →recent activity
Analyzing
Block #102,406,777
160 transactions · 64 stateful · 2026-09-06 07:13:21 UTC
Parallelism
87/100
Blocked
77%
Avg conflicts / tx
1.99
Longest chain
21 deep
Execution timeline
did this block parallelize well?
view
block #102,406,777 · 160 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
1w02w13w26w37w412w513w614w715w819w920w1095w11109w12110w13111w14112w15115w16157w17158w18159w19
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1c53de93…ac02
0xd32edf…ff58
39 touches
190 conflicts
0x00000000…0015
0x1b6862…e19c
28 touches
91 conflicts
0x00000000…001b
0x1b6862…e19c
28 touches
91 conflicts
0x00000000…002b
0x1b6862…e19c
28 touches
91 conflicts
0xba5743c7…21c2
0x1b6862…e19c
28 touches
91 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
28 touches
91 conflicts
0x00000000…0012
0x1b6862…e19c
28 touches
91 conflicts
0x00000000…0013
0x1b6862…e19c
28 touches
91 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
190 conflicts on slot 0x1c53de9364…0eac02
Audit this contract →
← previous block·next block →recent activity