← previous blocknext block →recent activity
Analyzing
Block #73,496,623
11 transactions · 9 stateful · 2026-05-09 16:48:52 UTC
Parallelism
55/100
Blocked
44%
Avg conflicts / tx
0.82
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #73,496,623 · 11 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w06w17w28w39w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4d87512b…897c
0x065c9d…c394
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x22e295f5…1bef
0x065c9d…c394
4 touches
1 conflict
0x00000000…0001
0x192600…8550
2 touches
0 conflicts
0x00000000…0003
0x192600…8550
2 touches
0 conflicts
0x06db03a6…4692
0x34b655…2a6f
2 touches
0 conflicts
0x42deeec2…4566
0x34b655…2a6f
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
6 conflicts on slot 0x4d87512b00…43897c
Audit this contract →
← previous block·next block →recent activity