← previous blocknext block →recent activity
Analyzing
Block #112,608,958
25 transactions · 24 stateful · 2026-10-12 00:14:28 UTC
Parallelism
80/100
Blocked
38%
Avg conflicts / tx
0.68
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #112,608,958 · 25 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w06w18w110w215w217w018w119w321w022w124w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe365edbc…38f7
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
8 touches
6 conflicts
0x261261a7…6175
0x1b6862…e19c
8 touches
6 conflicts
0x00000000…002f
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0040
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0058
0x1b6862…e19c
6 touches
3 conflicts
0x01e7b865…6e6d
0x188d58…ea8e
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
10 conflicts on slot 0xe365edbcf7…e838f7
Audit this contract →
← previous block·next block →recent activity