← previous blocknext block →recent activity
Analyzing
Block #73,811,120
7 transactions · 6 stateful · 2026-05-11 03:57:40 UTC
Parallelism
71/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,811,120 · 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
2w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e295f5…1bef
0x065c9d…c394
4 touches
1 conflict
0x5d9cfbb6…faba
0x065c9d…c394
3 touches
1 conflict
0x29434847…a44b
0x065c9d…c394
3 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x489c5683…8119
0x065c9d…c394
2 touches
0 conflicts
0x4d87512b…897c
0x065c9d…c394
2 touches
0 conflicts
0x6b1d8759…c965
0x065c9d…c394
2 touches
0 conflicts
0x9c816e80…9d30
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 0x22e295f5d8…ac1bef
Audit this contract →
← previous block·next block →recent activity