← previous blocknext block →recent activity
Analyzing
Block #73,642,713
7 transactions · 7 stateful · 2026-05-10 09:02:06 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,642,713 · 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
1w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x68dd470e…d3b0
0x065c9d…c394
4 touches
1 conflict
0x4086e061…897f
0x065c9d…c394
3 touches
1 conflict
0x5713276b…1d81
0x065c9d…c394
3 touches
1 conflict
0x22e295f5…1bef
0x065c9d…c394
2 touches
0 conflicts
0x4f2b9ef6…f55f
0x065c9d…c394
2 touches
0 conflicts
0x9473a13d…2ee8
0x065c9d…c394
2 touches
0 conflicts
0xd295d35c…714a
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
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 0x68dd470e43…4dd3b0
Audit this contract →
← previous block·next block →recent activity