← previous blocknext block →recent activity
Analyzing
Block #73,696,829
9 transactions · 9 stateful · 2026-05-10 15:07:02 UTC
Parallelism
67/100
Blocked
22%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,696,829 · 9 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
0xd5b99f38…e17e
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x0ac31945…2c72
0x065c9d…c394
4 touches
1 conflict
0x6e0ce9d7…bce9
0x065c9d…c394
2 touches
0 conflicts
0x85f93112…18d2
0x065c9d…c394
2 touches
0 conflicts
0xc8a3ba06…aca2
0x065c9d…c394
2 touches
0 conflicts
0xef50ac34…acbb
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 0xd5b99f38a9…5ae17e
Audit this contract →
← previous block·next block →recent activity