← previous blocknext block →recent activity
Analyzing
Block #112,082,526
27 transactions · 23 stateful · 2026-10-10 04:05:55 UTC
Parallelism
59/100
Blocked
52%
Avg conflicts / tx
2.15
Longest chain
11 deep
Execution timeline
did this block parallelize well?
view
block #112,082,526 · 27 txs across 11 waves · depth 11
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w810w911w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x60fef03f…2096
0xd32edf…ff58
21 touches
55 conflicts
0xd5b10148…e635
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…004c
0x80c745…7210
6 touches
3 conflicts
0x00000000…001c
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002c
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0040
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
55 conflicts on slot 0x60fef03f40…842096
Audit this contract →
← previous block·next block →recent activity