← previous blocknext block →recent activity
Analyzing
Block #73,687,386
20 transactions · 17 stateful · 2026-05-10 14:03:24 UTC
Parallelism
60/100
Blocked
59%
Avg conflicts / tx
1.4
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #73,687,386 · 20 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w37w48w411w512w613w715w516w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0x20bfc16d…9da6
0xd32edf…ff58
9 touches
10 conflicts
0x0ac31945…2c72
0x065c9d…c394
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0x8c40de05…13a1
0x065c9d…c394
5 touches
3 conflicts
0xf1a1cbfc…5220
0x065c9d…c394
5 touches
3 conflicts
0x00000000…0012
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
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity