← previous blocknext block →recent activity
Analyzing
Block #73,806,972
7 transactions · 6 stateful · 2026-05-11 03:30:01 UTC
Parallelism
57/100
Blocked
33%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,806,972 · 7 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
4w05w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4d87512b…897c
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x0819ff02…0378
0x065c9d…c394
2 touches
0 conflicts
0x1f4e73e8…08ed
0x065c9d…c394
2 touches
0 conflicts
0x45a4af3b…632e
0x065c9d…c394
2 touches
0 conflicts
0x519d8311…7acb
0x065c9d…c394
2 touches
0 conflicts
0xb33e5626…6951
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
3 conflicts on slot 0x4d87512b00…43897c
Audit this contract →
← previous block·next block →recent activity