← previous blocknext block →recent activity
Analyzing
Block #73,479,132
18 transactions · 15 stateful · 2026-05-09 14:52:29 UTC
Parallelism
61/100
Blocked
53%
Avg conflicts / tx
0.78
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #73,479,132 · 18 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w26w39w410w511w612w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f08361d…bda6
0x065c9d…c394
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x0a9146e6…f82a
0xd32edf…ff58
5 touches
3 conflicts
0xf537eaa0…73c8
0x065c9d…c394
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x9dc69c2f…00f1
0x065c9d…c394
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
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
6 conflicts on slot 0x6f08361da9…89bda6
Audit this contract →
← previous block·next block →recent activity