← previous blocknext block →recent activity
Analyzing
Block #73,911,921
9 transactions · 7 stateful · 2026-05-11 15:09:01 UTC
Parallelism
67/100
Blocked
29%
Avg conflicts / tx
0.22
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,911,921 · 9 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
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xbd7e37a9…9eb5
0x065c9d…c394
4 touches
1 conflict
0x2d6a14af…7e89
0x065c9d…c394
4 touches
1 conflict
0x8e6f638b…fee9
0x065c9d…c394
4 touches
1 conflict
0x9b305a93…19b6
0x065c9d…c394
3 touches
1 conflict
0x0261c7b5…cde6
0xd32edf…ff58
3 touches
1 conflict
0x957b6fcd…768a
0x065c9d…c394
3 touches
1 conflict
0x00000000…0019
0x1b6862…e19c
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