← previous blocknext block →recent activity
Analyzing
Block #73,504,526
9 transactions · 8 stateful · 2026-05-09 17:41:36 UTC
Parallelism
67/100
Blocked
38%
Avg conflicts / tx
0.56
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,504,526 · 9 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
1w02w13w17w08w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4d87512b…897c
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x489f2435…d13a
0xd32edf…ff58
3 touches
1 conflict
0x3cdfc713…a263
0x065c9d…c394
2 touches
0 conflicts
0x46f4e421…e0c2
0x065c9d…c394
2 touches
0 conflicts
0x8227deb9…9922
0x065c9d…c394
2 touches
0 conflicts
0xdaa5411e…afb2
0x065c9d…c394
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
3 conflicts on slot 0x4d87512b00…43897c
Audit this contract →
← previous block·next block →recent activity