← previous blocknext block →recent activity
Analyzing
Block #73,480,492
10 transactions · 8 stateful · 2026-05-09 15:01:30 UTC
Parallelism
60/100
Blocked
50%
Avg conflicts / tx
0.8
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,480,492 · 10 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
2w04w16w17w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0x211dc0fe…3251
0x065c9d…c394
4 touches
1 conflict
0xed78772c…bc00
0x065c9d…c394
4 touches
1 conflict
0x5b3f6fd0…432c
0x065c9d…c394
3 touches
1 conflict
0x8c9cb054…1d47
0x065c9d…c394
3 touches
1 conflict
0x3345ced8…8a23
0x065c9d…c394
3 touches
1 conflict
0xdee29b69…3a2e
0x065c9d…c394
3 touches
1 conflict
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