← previous blocknext block →recent activity
Analyzing
Block #105,470,787
25 transactions · 24 stateful · 2026-09-17 01:11:01 UTC
Parallelism
60/100
Blocked
75%
Avg conflicts / tx
2.2
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #105,470,787 · 25 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w610w713w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4abb1c35…a1db
0xd32edf…ff58
15 touches
28 conflicts
0xca841faa…486a
0x34b655…2a6f
12 touches
15 conflicts
0xaad6be10…0801
0x2a68ba…90c5
8 touches
6 conflicts
0xa4f80979…4d71
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0018
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0028
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
28 conflicts on slot 0x4abb1c354e…2fa1db
Audit this contract →
← previous block·next block →recent activity