← previous blocknext block →recent activity
Analyzing
Block #101,298,279
30 transactions · 21 stateful · 2026-09-02 09:57:12 UTC
Parallelism
67/100
Blocked
57%
Avg conflicts / tx
1.1
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #101,298,279 · 30 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w15w26w37w48w510w523w628w829w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6b60d8f4…d5ef
0xd32edf…ff58
13 touches
21 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xba5743c7…21c3
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002c
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0012
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
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 0x6b60d8f459…7ad5ef
Audit this contract →
← previous block·next block →recent activity