← previous blocknext block →recent activity
Analyzing
Block #72,395,285
33 transactions · 24 stateful · 2026-05-04 14:35:46 UTC
Parallelism
73/100
Blocked
54%
Avg conflicts / tx
1.09
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #72,395,285 · 33 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w07w311w217w119w422w423w524w525w626w727w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5c8c6ab6…dc36
0x065c9d…c394
12 touches
15 conflicts
0x00000000…003d
0x065c9d…c394
12 touches
15 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
8 touches
6 conflicts
0x34ceb768…1dbc
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…001a
0x1b6862…e19c
6 touches
3 conflicts
0xada193dc…5c7b
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002a
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 0x5c8c6ab6f0…86dc36
Audit this contract →
← previous block·next block →recent activity