← previous blocknext block →recent activity
Analyzing
Block #95,783,209
19 transactions · 16 stateful · 2026-08-14 01:13:50 UTC
Parallelism
68/100
Blocked
50%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #95,783,209 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w47w08w19w010w513w114w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1fe803c7…b37b
0xd32edf…ff58
11 touches
15 conflicts
0xe8eae8a3…bacc
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0xae4250f1…df69
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…001e
0x1b6862…e19c
2 touches
0 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
15 conflicts on slot 0x1fe803c7c6…02b37b
Audit this contract →
← previous block·next block →recent activity