← previous blocknext block →recent activity
Analyzing
Block #73,394,226
9 transactions · 9 stateful · 2026-05-09 05:27:27 UTC
Parallelism
78/100
Blocked
11%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,394,226 · 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
1w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbff3a6fa…4b83
0x065c9d…c394
4 touches
1 conflict
0x4d87512b…897c
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x2b6308f9…46f1
0x065c9d…c394
3 touches
1 conflict
0x0c3b7fd9…4426
0x065c9d…c394
3 touches
1 conflict
0x79bd3c69…38e1
0x065c9d…c394
2 touches
0 conflicts
0x9d5fef78…f496
0x065c9d…c394
2 touches
0 conflicts
0xeb6e9d8e…5380
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 0xbff3a6fa6a…a54b83
Audit this contract →
← previous block·next block →recent activity