← previous blocknext block →recent activity
Analyzing
Block #73,924,375
28 transactions · 22 stateful · 2026-05-11 16:32:03 UTC
Parallelism
64/100
Blocked
64%
Avg conflicts / tx
1.64
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #73,924,375 · 28 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w510w616w717w818w619w720w822w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf537eaa0…73c8
0x065c9d…c394
12 touches
15 conflicts
0x00000000…003d
0x065c9d…c394
12 touches
15 conflicts
0x4d6648d4…c233
0xd32edf…ff58
9 touches
10 conflicts
0x046a928e…0012
0x2a68ba…90c5
8 touches
6 conflicts
0x6f08361d…bda6
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 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
15 conflicts on slot 0xf537eaa0c6…3873c8
Audit this contract →
← previous block·next block →recent activity