← previous blocknext block →recent activity
Analyzing
Block #73,416,975
9 transactions · 8 stateful · 2026-05-09 07:58:57 UTC
Parallelism
56/100
Blocked
38%
Avg conflicts / tx
0.67
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #73,416,975 · 9 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w15w26w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xf537eaa0…73c8
0x065c9d…c394
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0x3ed03557…f175
0x065c9d…c394
3 touches
1 conflict
0xd735aeed…ebc5
0x065c9d…c394
3 touches
1 conflict
0x440621bb…933e
0x065c9d…c394
2 touches
0 conflicts
0x57c65674…f7ea
0x065c9d…c394
2 touches
0 conflicts
0x5bfd2e59…4fde
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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity