← previous blocknext block →recent activity
Analyzing
Block #72,271,073
13 transactions · 10 stateful · 2026-05-04 00:46:48 UTC
Parallelism
85/100
Blocked
10%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #72,271,073 · 13 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
1w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xae7c69bf…0168
0x065c9d…c394
4 touches
1 conflict
0x07bfb56d…3358
0x065c9d…c394
3 touches
1 conflict
0x41755291…977f
0x065c9d…c394
2 touches
0 conflicts
0x47b807a2…3307
0x065c9d…c394
2 touches
0 conflicts
0x48ad6cda…ff16
0x065c9d…c394
2 touches
0 conflicts
0x815e5dcc…819a
0x065c9d…c394
2 touches
0 conflicts
0x930f80ab…1afe
0x065c9d…c394
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity