← previous blocknext block →recent activity
Analyzing
Block #73,696,953
9 transactions · 8 stateful · 2026-05-10 15:07:53 UTC
Parallelism
56/100
Blocked
38%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,696,953 · 9 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
1w04w16w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x0ac31945…2c72
0x065c9d…c394
4 touches
1 conflict
0x56480508…ac9c
0x065c9d…c394
4 touches
1 conflict
0x197ad861…6bb3
0x065c9d…c394
3 touches
1 conflict
0x8eb939b8…b274
0x065c9d…c394
3 touches
1 conflict
0xb3855eb0…0f71
0x065c9d…c394
3 touches
1 conflict
0x968bdacb…f461
0x2a68ba…90c5
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