← previous blocknext block →recent activity
Analyzing
Block #101,022,478
23 transactions · 19 stateful · 2026-09-01 10:49:22 UTC
Parallelism
74/100
Blocked
58%
Avg conflicts / tx
1.04
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #101,022,478 · 23 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w15w39w410w511w012w113w214w317w221w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbddd34cf…3fc5
0xd32edf…ff58
11 touches
15 conflicts
0xf79df061…e005
0xe52b14…7230
8 touches
6 conflicts
0x57070322…bc66
0xe52b14…7230
8 touches
6 conflicts
0xba5743c7…21c6
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…001f
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
15 conflicts on slot 0xbddd34cf8a…4f3fc5
Audit this contract →
← previous block·next block →recent activity