← previous blocknext block →recent activity
Analyzing
Block #73,925,890
19 transactions · 12 stateful · 2026-05-11 16:42:09 UTC
Parallelism
63/100
Blocked
58%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #73,925,890 · 19 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w511w613w014w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5d16fd3c…409f
0xd32edf…ff58
11 touches
15 conflicts
0x6aa624fd…a84c
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0013
0x1b6862…e19c
10 touches
10 conflicts
0x00000000…0015
0x1b6862…e19c
10 touches
10 conflicts
0x01e7b865…6e6f
0x188d58…ea8e
8 touches
6 conflicts
0x01e7b865…6e6d
0x188d58…ea8e
8 touches
6 conflicts
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x522477de…2714
0x0555e3…2b9c
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
15 conflicts on slot 0x5d16fd3ce5…f1409f
Audit this contract →
← previous block·next block →recent activity