← previous blocknext block →recent activity
Analyzing
Block #73,600,722
12 transactions · 11 stateful · 2026-05-10 04:20:47 UTC
Parallelism
83/100
Blocked
9%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,600,722 · 12 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
1w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x94d3c2f4…624b
0x065c9d…c394
3 touches
1 conflict
0x0b838744…0a87
0x065c9d…c394
3 touches
1 conflict
0x6d8ac73a…b1f6
0x065c9d…c394
2 touches
0 conflicts
0x6e6274e1…ae4d
0x065c9d…c394
2 touches
0 conflicts
0x6f08361d…bda6
0x065c9d…c394
2 touches
0 conflicts
0xd60ef6a2…43e8
0x065c9d…c394
2 touches
0 conflicts
0xd7b7c3c7…c3ae
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