← previous blocknext block →recent activity
Analyzing
Block #73,389,774
12 transactions · 11 stateful · 2026-05-09 04:57:47 UTC
Parallelism
75/100
Blocked
18%
Avg conflicts / tx
0.42
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,389,774 · 12 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w06w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x4d87512b…897c
0x065c9d…c394
4 touches
1 conflict
0x21c3fbdb…ace5
0x065c9d…c394
2 touches
0 conflicts
0x494f047e…ee83
0x065c9d…c394
2 touches
0 conflicts
0x58e1721b…c52d
0x065c9d…c394
2 touches
0 conflicts
0x5ac3080f…35b4
0x065c9d…c394
2 touches
0 conflicts
0x63236917…1526
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity