← previous blocknext block →recent activity
Analyzing
Block #73,513,303
14 transactions · 12 stateful · 2026-05-09 18:39:58 UTC
Parallelism
43/100
Blocked
58%
Avg conflicts / tx
2
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #73,513,303 · 14 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
1w02w13w24w35w46w57w68w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x95e80650…06f4
0xd32edf…ff58
15 touches
28 conflicts
0x00000000…0019
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…0029
0x1b6862…e19c
4 touches
1 conflict
0xd8d828a7…b649
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
28 conflicts on slot 0x95e80650b0…2e06f4
Audit this contract →
← previous block·next block →recent activity