← previous blocknext block →recent activity
Analyzing
Block #81,623,856
20 transactions · 16 stateful · 2026-06-16 08:31:22 UTC
Parallelism
75/100
Blocked
50%
Avg conflicts / tx
0.8
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #81,623,856 · 20 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
1w02w13w24w37w08w09w110w111w216w217w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f5be59d…d843
0xd32edf…ff58
9 touches
10 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x7d42dc8b…fdb6
0x2a68ba…90c5
6 touches
3 conflicts
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
0x37699b20…1072
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
10 conflicts on slot 0x6f5be59d1b…96d843
Audit this contract →
← previous block·next block →recent activity