← previous blocknext block →recent activity
Analyzing
Block #72,271,258
14 transactions · 9 stateful · 2026-05-04 00:48:04 UTC
Parallelism
86/100
Blocked
11%
Avg conflicts / tx
0.07
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #72,271,258 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
8w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xae7c69bf…0168
0x065c9d…c394
4 touches
1 conflict
0xc5c3fe8b…6322
0x065c9d…c394
3 touches
1 conflict
0xbb63b9c2…b7ee
0x065c9d…c394
3 touches
1 conflict
0x005fb969…2d97
0x34b655…2a6f
2 touches
0 conflicts
0x0520da1d…c88e
0x34b655…2a6f
2 touches
0 conflicts
0x085df2c1…305a
0x34b655…2a6f
2 touches
0 conflicts
0x104887dc…9894
0x34b655…2a6f
2 touches
0 conflicts
0x1608635c…d25d
0x34b655…2a6f
2 touches
0 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
1 conflict on slot 0xae7c69bf16…760168
Audit this contract →
← previous block·next block →recent activity