← previous blocknext block →recent activity
Analyzing
Block #75,866,606
19 transactions · 15 stateful · 2026-05-20 16:41:51 UTC
Parallelism
58/100
Blocked
47%
Avg conflicts / tx
1.47
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #75,866,606 · 19 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w511w618w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbf537e79…279f
0xd32edf…ff58
15 touches
28 conflicts
0xd9f18d9a…141d
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…0018
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0028
0x1b6862…e19c
4 touches
1 conflict
0x65bd5770…5eca
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
28 conflicts on slot 0xbf537e797c…2d279f
Audit this contract →
← previous block·next block →recent activity