← previous blocknext block →recent activity
Analyzing
Block #73,437,583
13 transactions · 9 stateful · 2026-05-09 10:15:59 UTC
Parallelism
69/100
Blocked
44%
Avg conflicts / tx
0.54
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,437,583 · 13 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w16w07w18w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x4d87512b…897c
0x065c9d…c394
5 touches
3 conflicts
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0x56eee8ec…aa40
0x065c9d…c394
2 touches
0 conflicts
0x77c8d47a…89b4
0x065c9d…c394
2 touches
0 conflicts
0x8ac7dc79…20e4
0x065c9d…c394
2 touches
0 conflicts
0x8c6bbffa…68da
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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity