← previous blocknext block →recent activity
Analyzing
Block #106,959,113
14 transactions · 14 stateful · 2026-09-22 06:05:17 UTC
Parallelism
64/100
Blocked
36%
Avg conflicts / tx
0.57
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #106,959,113 · 14 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
1w02w13w24w38w410w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1ad7af21…2e51
0xd32edf…ff58
7 touches
6 conflicts
0x75e73565…45fa
0x1b6862…e19c
4 touches
1 conflict
0x77ed432f…fa04
0x065c9d…c394
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001e
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002e
0x1b6862…e19c
4 touches
1 conflict
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 0x1ad7af217e…f42e51
Audit this contract →
← previous block·next block →recent activity