← previous blocknext block →recent activity
Analyzing
Block #102,311,965
39 transactions · 26 stateful · 2026-09-05 23:13:01 UTC
Parallelism
80/100
Blocked
46%
Avg conflicts / tx
0.87
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #102,311,965 · 39 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
2w03w14w29w312w114w425w426w537w638w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2507e19b…a857
0xd32edf…ff58
15 touches
28 conflicts
0xaad6be10…0801
0x2a68ba…90c5
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…0019
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0029
0x1b6862…e19c
6 touches
3 conflicts
0xba5743c7…21c0
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
28 conflicts on slot 0x2507e19bad…ffa857
Audit this contract →
← previous block·next block →recent activity