← previous blocknext block →recent activity
Analyzing
Block #73,037,463
16 transactions · 12 stateful · 2026-05-07 13:53:52 UTC
Parallelism
88/100
Blocked
25%
Avg conflicts / tx
0.19
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,037,463 · 16 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
2w03w16w07w18w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x1eba9ac2…e2bb
0x065c9d…c394
4 touches
1 conflict
0x24aa733e…f092
0x065c9d…c394
4 touches
1 conflict
0x44450884…5e69
0x065c9d…c394
4 touches
1 conflict
0xb14682e3…5933
0x065c9d…c394
4 touches
1 conflict
0xbf6827d3…fdb5
0x065c9d…c394
4 touches
1 conflict
0xc8ada8eb…7a29
0x065c9d…c394
4 touches
1 conflict
0x60f7fbaf…bd58
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity