← previous blocknext block →recent activity
Analyzing
Block #72,398,925
34 transactions · 18 stateful · 2026-05-04 15:00:03 UTC
Parallelism
85/100
Blocked
56%
Avg conflicts / tx
0.59
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #72,398,925 · 34 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w120w021w122w224w225w226w327w431w232w333w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xbbee74c2…567a
0x065c9d…c394
8 touches
6 conflicts
0xa800bb04…1d40
0x34b655…2a6f
6 touches
3 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xbad68552…e6bf
0x34b655…2a6f
6 touches
3 conflicts
0x24968e6d…0132
0x065c9d…c394
6 touches
3 conflicts
0xf2360fa7…c55c
0xd32edf…ff58
5 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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity