← previous blocknext block →recent activity
Analyzing
Block #102,480,200
40 transactions · 26 stateful · 2026-09-06 13:25:19 UTC
Parallelism
77/100
Blocked
54%
Avg conflicts / tx
1.23
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #102,480,200 · 40 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w29w311w414w515w616w730w837w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb56c05bb…21cd
0xd32edf…ff58
17 touches
36 conflicts
0xc5c24509…7332
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001c
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002c
0x1b6862…e19c
8 touches
6 conflicts
0xba5743c7…21c3
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
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
36 conflicts on slot 0xb56c05bbfb…2621cd
Audit this contract →
← previous block·next block →recent activity