← previous blocknext block →recent activity
Analyzing
Block #105,542,244
24 transactions · 21 stateful · 2026-09-17 07:10:37 UTC
Parallelism
79/100
Blocked
57%
Avg conflicts / tx
1.17
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #105,542,244 · 24 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
1w02w13w24w26w07w08w111w312w413w216w217w318w323w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbada5ae1…3e18
0xd32edf…ff58
9 touches
10 conflicts
0x86bd79a5…1f48
0x34b655…2a6f
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
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…0019
0x1b6862…e19c
8 touches
6 conflicts
0xf9e48d0a…6baa
0x34b655…2a6f
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 0xbada5ae1f3…6e3e18
Audit this contract →
← previous block·next block →recent activity