← previous blocknext block →recent activity
Analyzing
Block #102,809,343
36 transactions · 28 stateful · 2026-09-07 17:10:01 UTC
Parallelism
78/100
Blocked
64%
Avg conflicts / tx
1.47
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #102,809,343 · 36 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w610w226w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc615fab6…b204
0xd32edf…ff58
15 touches
28 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x511f46a7…edab
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x451e482b…7e7d
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001b
0x1b6862…e19c
8 touches
6 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
28 conflicts on slot 0xc615fab6a8…39b204
Audit this contract →
← previous block·next block →recent activity