← previous blocknext block →recent activity
Analyzing
Block #81,623,870
22 transactions · 18 stateful · 2026-06-16 08:31:28 UTC
Parallelism
55/100
Blocked
56%
Avg conflicts / tx
2.09
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #81,623,870 · 22 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
1w02w13w24w35w46w57w68w713w814w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x410158dd…c356
0xd32edf…ff58
19 touches
45 conflicts
0x580c6fe7…0fe5
0x1b6862…e19c
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…001b
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002b
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
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
45 conflicts on slot 0x410158ddf0…6fc356
Audit this contract →
← previous block·next block →recent activity