← previous blocknext block →recent activity
Analyzing
Block #73,603,996
10 transactions · 9 stateful · 2026-05-10 04:42:30 UTC
Parallelism
70/100
Blocked
33%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,603,996 · 10 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
2w04w15w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcd5417e6…1963
0x065c9d…c394
4 touches
1 conflict
0xda94753a…053e
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x134648f7…7077
0x065c9d…c394
4 touches
1 conflict
0x7fe278ad…9265
0x065c9d…c394
3 touches
1 conflict
0xc659a676…d9b2
0x065c9d…c394
3 touches
1 conflict
0x0f89d8b5…b604
0x065c9d…c394
3 touches
1 conflict
0x7e69b59c…7956
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
1 conflict on slot 0xcd5417e6ad…1b1963
Audit this contract →
← previous block·next block →recent activity