← previous blocknext block →recent activity
Analyzing
Block #73,324,117
10 transactions · 8 stateful · 2026-05-08 21:41:07 UTC
Parallelism
80/100
Blocked
13%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #73,324,117 · 10 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
1w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xe094464b…1f65
0x065c9d…c394
3 touches
1 conflict
0xcf5b73b5…4e82
0x065c9d…c394
3 touches
1 conflict
0x6f08361d…bda6
0x065c9d…c394
2 touches
0 conflicts
0x810f2a29…4f29
0x065c9d…c394
2 touches
0 conflicts
0x89dd0bb9…9f6a
0x065c9d…c394
2 touches
0 conflicts
0xf22f7e88…7fc2
0x065c9d…c394
2 touches
0 conflicts
0xf537eaa0…73c8
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