← previous blocknext block →recent activity
Analyzing
Block #73,923,028
16 transactions · 12 stateful · 2026-05-11 16:23:06 UTC
Parallelism
50/100
Blocked
67%
Avg conflicts / tx
1.44
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #73,923,028 · 16 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
1w02w13w24w35w46w57w612w613w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5a228c7a…7c3e
0xd32edf…ff58
13 touches
21 conflicts
0x44d7acbf…e67b
0x1b6862…e19c
4 touches
1 conflict
0x00000000…003d
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…0019
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0029
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
21 conflicts on slot 0x5a228c7a1f…ca7c3e
Audit this contract →
← previous block·next block →recent activity