← previous blocknext block →recent activity
Analyzing
Block #76,107,620
25 transactions · 19 stateful · 2026-05-21 19:27:10 UTC
Parallelism
60/100
Blocked
58%
Avg conflicts / tx
1.4
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #76,107,620 · 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
1w02w13w24w35w46w57w610w711w814w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x35f14343…e01e
0xd32edf…ff58
13 touches
21 conflicts
0x41755291…977f
0x065c9d…c394
12 touches
15 conflicts
0x00000000…002d
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0012
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…001d
0x1b6862…e19c
10 touches
10 conflicts
0x65bd5770…5ecf
0x1b6862…e19c
10 touches
10 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
21 conflicts on slot 0x35f143431b…73e01e
Audit this contract →
← previous block·next block →recent activity