← previous blocknext block →recent activity
Analyzing
Block #72,971,080
52 transactions · 32 stateful · 2026-05-07 06:32:01 UTC
Parallelism
85/100
Blocked
56%
Avg conflicts / tx
1.06
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #72,971,080 · 52 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
1w02w13w24w35w47w510w511w630w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
14 touches
21 conflicts
0x5b151427…50e0
0xd32edf…ff58
13 touches
21 conflicts
0x17606ba6…1b6e
0x754704…b603
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0x7f189cf6…afab
0x065c9d…c394
8 touches
6 conflicts
0x0eac6378…36f4
0x34b655…2a6f
6 touches
3 conflicts
0x13391aa3…58c7
0x34b655…2a6f
6 touches
3 conflicts
0x150af51d…9c42
0x34b655…2a6f
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
21 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity