← previous blocknext block →recent activity
Analyzing
Block #110,207,824
32 transactions · 29 stateful · 2026-10-03 14:47:07 UTC
Parallelism
78/100
Blocked
31%
Avg conflicts / tx
0.75
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #110,207,824 · 32 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w614w015w116w129w031w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x578f6003…06bf
0xd32edf…ff58
13 touches
21 conflicts
0x0e64cf42…c999
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…001f
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…002f
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0040
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0058
0x1b6862…e19c
10 touches
10 conflicts
0x1c7e70e2…fc21
0x1b6862…e19c
10 touches
10 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 0x578f60037d…cd06bf
Audit this contract →
← previous block·next block →recent activity