← previous blocknext block →recent activity
Analyzing
Block #73,216,446
13 transactions · 13 stateful · 2026-05-08 09:44:42 UTC
Parallelism
77/100
Blocked
15%
Avg conflicts / tx
0.15
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,216,446 · 13 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
1w02w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5f96bdd1…5e91
0x065c9d…c394
4 touches
1 conflict
0xdc299592…65c9
0x065c9d…c394
4 touches
1 conflict
0x0b390c61…dc07
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x6411ea12…7975
0x065c9d…c394
2 touches
0 conflicts
0x85064be6…797d
0x065c9d…c394
2 touches
0 conflicts
0x92c60916…fe4d
0x065c9d…c394
2 touches
0 conflicts
0x9c72a8d1…162b
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 0x5f96bdd1f0…085e91
Audit this contract →
← previous block·next block →recent activity