← previous blocknext block →recent activity
Analyzing
Block #112,243,960
48 transactions · 46 stateful · 2026-10-10 17:38:05 UTC
Parallelism
65/100
Blocked
83%
Avg conflicts / tx
4.5
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #112,243,960 · 48 txs across 17 waves · depth 17
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w810w911w1012w1113w1214w1315w1416w1517w1628w129w230w331w432w433w534w635w737w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf35e2a28…d059
0xd32edf…ff58
33 touches
136 conflicts
0x00000000…0013
0x1b6862…e19c
30 touches
105 conflicts
0x00000000…0015
0x1b6862…e19c
30 touches
105 conflicts
0xd4c913d7…343f
0x1b6862…e19c
30 touches
105 conflicts
0x00000000…0058
0x1b6862…e19c
16 touches
28 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
16 touches
28 conflicts
0x8bd52e92…4b58
0x1b6862…e19c
16 touches
28 conflicts
0x00000000…0012
0x1b6862…e19c
16 touches
28 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
136 conflicts on slot 0xf35e2a2893…26d059
Audit this contract →
← previous block·next block →recent activity