← previous blocknext block →recent activity
Analyzing
Block #73,396,335
7 transactions · 7 stateful · 2026-05-09 05:41:29 UTC
Parallelism
71/100
Blocked
14%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,396,335 · 7 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb3f5304f…1d16
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xad8a34f8…04cf
0x065c9d…c394
3 touches
1 conflict
0x2224dc93…f72b
0x065c9d…c394
2 touches
0 conflicts
0x22e295f5…1bef
0x065c9d…c394
2 touches
0 conflicts
0x48bdea5f…959e
0x065c9d…c394
2 touches
0 conflicts
0x4d87512b…897c
0x065c9d…c394
2 touches
0 conflicts
0x690ac2e1…b98b
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 0xb3f5304fdb…121d16
Audit this contract →
← previous block·next block →recent activity