← previous blocknext block →recent activity
Analyzing
Block #110,208,133
20 transactions · 17 stateful · 2026-10-03 14:48:40 UTC
Parallelism
80/100
Blocked
29%
Avg conflicts / tx
0.4
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #110,208,133 · 20 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w312w015w116w019w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4fb400c1…9617
0xd32edf…ff58
7 touches
6 conflicts
0xf91b744e…9117
0x754704…b603
6 touches
3 conflicts
0x6af306bb…2e81
0x3bd359…433a
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001f
0x1b6862…e19c
6 touches
3 conflicts
0xd987be6c…47f1
0x754704…b603
6 touches
3 conflicts
0x6235638c…643d
0x1b6862…e19c
6 touches
3 conflicts
0xcb45d9d6…cb87
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
6 conflicts on slot 0x4fb400c1ae…d79617
Audit this contract →
← previous block·next block →recent activity