← previous blocknext block →recent activity
Analyzing
Block #112,612,789
30 transactions · 28 stateful · 2026-10-12 00:33:45 UTC
Parallelism
80/100
Blocked
36%
Avg conflicts / tx
0.73
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #112,612,789 · 30 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w05w17w08w19w210w316w117w218w319w422w425w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x721977d9…8417
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0002
0x125f12…a50b
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…001f
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002f
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0058
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
10 conflicts on slot 0x721977d9c0…c58417
Audit this contract →
← previous block·next block →recent activity