← previous blocknext block →recent activity
Analyzing
Block #73,416,463
13 transactions · 11 stateful · 2026-05-09 07:55:31 UTC
Parallelism
62/100
Blocked
36%
Avg conflicts / tx
0.77
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #73,416,463 · 13 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w16w27w38w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x046a928e…0012
0x2a68ba…90c5
8 touches
6 conflicts
0xf537eaa0…73c8
0x065c9d…c394
6 touches
3 conflicts
0xc42c6c6e…b55b
0x065c9d…c394
3 touches
1 conflict
0x2136dae8…330f
0x065c9d…c394
3 touches
1 conflict
0xa33757c0…29e5
0x065c9d…c394
3 touches
1 conflict
0x9bb757f6…701f
0x065c9d…c394
3 touches
1 conflict
0x4880c0ed…4302
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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity