← previous blocknext block →recent activity
Analyzing
Block #73,990,829
11 transactions · 9 stateful · 2026-05-11 23:55:38 UTC
Parallelism
82/100
Blocked
11%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,990,829 · 11 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
1w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0c38465d…a3d8
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x7b627914…e452
0x065c9d…c394
3 touches
1 conflict
0x1ec89436…e82e
0x065c9d…c394
2 touches
0 conflicts
0x3861635c…5a17
0x065c9d…c394
2 touches
0 conflicts
0x560039db…772f
0x065c9d…c394
2 touches
0 conflicts
0xf537eaa0…73c8
0x065c9d…c394
2 touches
0 conflicts
0xea02471d…1539
0x34b655…2a6f
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 0x0c38465def…20a3d8
Audit this contract →
← previous block·next block →recent activity