← previous blocknext block →recent activity
Analyzing
Block #73,307,946
10 transactions · 10 stateful · 2026-05-08 19:53:27 UTC
Parallelism
80/100
Blocked
20%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,307,946 · 10 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
1w03w05w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0b390c61…dc07
0x065c9d…c394
4 touches
1 conflict
0x5f6b7d88…cbd8
0x065c9d…c394
4 touches
1 conflict
0xf853eb8e…4027
0x34b655…2a6f
4 touches
1 conflict
0xbd7e37a9…9eb5
0x065c9d…c394
4 touches
1 conflict
0x1b9e654e…0a08
0x34b655…2a6f
4 touches
1 conflict
0x42446806…33dd
0x34b655…2a6f
4 touches
1 conflict
0x6eba5e7f…4b52
0x34b655…2a6f
4 touches
1 conflict
0xa91c899f…6ee3
0x34b655…2a6f
4 touches
1 conflict
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 0x0b390c6160…02dc07
Audit this contract →
← previous block·next block →recent activity