← previous blocknext block →recent activity
Analyzing
Block #73,393,939
12 transactions · 10 stateful · 2026-05-09 05:25:32 UTC
Parallelism
75/100
Blocked
20%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,393,939 · 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
2w05w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x4d87512b…897c
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x93a015fe…0ed7
0x065c9d…c394
3 touches
1 conflict
0x324be288…00a3
0x065c9d…c394
2 touches
0 conflicts
0x7c53af72…1e6a
0x065c9d…c394
2 touches
0 conflicts
0x8fc92287…a933
0x065c9d…c394
2 touches
0 conflicts
0xbecacc36…435d
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