← previous blocknext block →recent activity
Analyzing
Block #101,967,351
24 transactions · 18 stateful · 2026-09-04 18:06:21 UTC
Parallelism
67/100
Blocked
44%
Avg conflicts / tx
1.04
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #101,967,351 · 24 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
1w02w13w24w35w417w518w619w423w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2bcd5ed2…b9c8
0xd32edf…ff58
13 touches
21 conflicts
0x73912233…4584
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001a
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002a
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
21 conflicts on slot 0x2bcd5ed269…f4b9c8
Audit this contract →
← previous block·next block →recent activity