← previous blocknext block →recent activity
Analyzing
Block #73,968,348
20 transactions · 15 stateful · 2026-05-11 21:24:32 UTC
Parallelism
60/100
Blocked
53%
Avg conflicts / tx
1.45
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #73,968,348 · 20 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
1w02w13w24w35w46w57w68w711w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbf1e0756…4c3d
0xd32edf…ff58
15 touches
28 conflicts
0x58e06bab…34cd
0x1b6862…e19c
4 touches
1 conflict
0x8662c204…af28
0x065c9d…c394
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…001a
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002a
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 0xbf1e07565a…644c3d
Audit this contract →
← previous block·next block →recent activity