← previous blocknext block →recent activity
Analyzing
Block #102,420,228
39 transactions · 21 stateful · 2026-09-06 08:21:28 UTC
Parallelism
87/100
Blocked
48%
Avg conflicts / tx
0.44
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,420,228 · 39 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w010w111w217w018w019w120w221w125w328w029w131w134w435w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0f436961…03a7
0xd32edf…ff58
9 touches
10 conflicts
0x580c6fe7…0fe5
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001b
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002b
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
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
10 conflicts on slot 0x0f43696172…3703a7
Audit this contract →
← previous block·next block →recent activity