← previous blocknext block →recent activity
Analyzing
Block #73,337,585
13 transactions · 11 stateful · 2026-05-08 23:10:38 UTC
Parallelism
85/100
Blocked
9%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,337,585 · 13 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
1w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xfa2c719d…1bce
0x065c9d…c394
4 touches
1 conflict
0xbd7e37a9…9eb5
0x065c9d…c394
4 touches
1 conflict
0x006a75a7…2153
0x065c9d…c394
3 touches
1 conflict
0x1f0a516c…b479
0x065c9d…c394
3 touches
1 conflict
0xbdbb7890…6a33
0x065c9d…c394
2 touches
0 conflicts
0xd8e0b79b…cebb
0x065c9d…c394
2 touches
0 conflicts
0xeada8f5a…fb9e
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity