← previous blocknext block →recent activity
Analyzing
Block #73,273,314
11 transactions · 10 stateful · 2026-05-08 16:03:01 UTC
Parallelism
73/100
Blocked
20%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,273,314 · 11 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
1w02w13w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0b390c61…dc07
0x065c9d…c394
4 touches
1 conflict
0x2e056be8…838a
0xd32edf…ff58
3 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x3e2b8142…85ac
0x065c9d…c394
2 touches
0 conflicts
0x9842e76d…06bb
0x065c9d…c394
2 touches
0 conflicts
0xcffcd23a…8f09
0x065c9d…c394
2 touches
0 conflicts
0xd9cae5b8…440f
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 0x0b390c6160…02dc07
Audit this contract →
← previous block·next block →recent activity