← previous blocknext block →recent activity
Analyzing
Block #73,336,014
10 transactions · 8 stateful · 2026-05-08 23:00:12 UTC
Parallelism
80/100
Blocked
13%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,336,014 · 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
1w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xe355bf38…faf1
0x065c9d…c394
4 touches
1 conflict
0xe19255b9…6620
0x065c9d…c394
3 touches
1 conflict
0xe6f50b44…2310
0x065c9d…c394
3 touches
1 conflict
0x5a4db224…eda5
0x065c9d…c394
2 touches
0 conflicts
0x979e5818…c903
0x065c9d…c394
2 touches
0 conflicts
0xc2ca2f6c…39a7
0x065c9d…c394
2 touches
0 conflicts
0xc787c16e…6f19
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity