← previous blocknext block →recent activity
Analyzing
Block #73,504,538
12 transactions · 9 stateful · 2026-05-09 17:41:41 UTC
Parallelism
75/100
Blocked
22%
Avg conflicts / tx
0.17
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,504,538 · 12 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x2fc02f23…4feb
0x065c9d…c394
4 touches
1 conflict
0x6d1aa6ec…502a
0x065c9d…c394
3 touches
1 conflict
0x5779cdf5…06b0
0xd32edf…ff58
3 touches
1 conflict
0x46f4e421…e0c2
0x065c9d…c394
2 touches
0 conflicts
0x5aa24f04…5af6
0x065c9d…c394
2 touches
0 conflicts
0x73ccfcb8…b5c1
0x065c9d…c394
2 touches
0 conflicts
0x09000000…0001
0x000000…1000
2 touches
0 conflicts
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: Kuru Exchange: Market-MON/USDC
1 conflict on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity