← previous blocknext block →recent activity
Analyzing
Block #73,991,730
9 transactions · 9 stateful · 2026-05-12 00:01:45 UTC
Parallelism
67/100
Blocked
22%
Avg conflicts / tx
0.22
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,991,730 · 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
1w03w14w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x68aa18e9…bcf7
0x065c9d…c394
4 touches
1 conflict
0xf537eaa0…73c8
0x065c9d…c394
4 touches
1 conflict
0x6f08361d…bda6
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xe57ab98f…80a5
0xd32edf…ff58
3 touches
1 conflict
0x97f3158d…ee38
0x065c9d…c394
3 touches
1 conflict
0x9cc1fc7d…7b43
0x065c9d…c394
3 touches
1 conflict
0xef6add38…d1ab
0x065c9d…c394
3 touches
1 conflict
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 0x68aa18e9e8…d1bcf7
Audit this contract →
← previous block·next block →recent activity