← previous blocknext block →recent activity
Analyzing
Block #73,643,486
9 transactions · 7 stateful · 2026-05-10 09:07:18 UTC
Parallelism
78/100
Blocked
14%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,643,486 · 9 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4d87512b…897c
0x065c9d…c394
4 touches
1 conflict
0x22e295f5…1bef
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x21d177a0…69c4
0x065c9d…c394
4 touches
1 conflict
0x3ac3ab09…e766
0x065c9d…c394
2 touches
0 conflicts
0x545fe721…684f
0x065c9d…c394
2 touches
0 conflicts
0x91e47116…31d1
0x065c9d…c394
2 touches
0 conflicts
0xdf8e4178…6beb
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
1 conflict on slot 0x4d87512b00…43897c
Audit this contract →
← previous block·next block →recent activity