← previous blocknext block →recent activity
Analyzing
Block #72,271,278
10 transactions · 10 stateful · 2026-05-04 00:48:12 UTC
Parallelism
80/100
Blocked
20%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #72,271,278 · 10 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
3w04w05w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x4267aa17…13b9
0x065c9d…c394
4 touches
1 conflict
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0x0663decc…d488
0x065c9d…c394
3 touches
1 conflict
0x8a35acfb…d1ac
0x8d66a4…3095
3 touches
1 conflict
0x357adf89…52e8
0x8d66a4…3095
3 touches
1 conflict
0x6b6a2dcc…cc15
0x065c9d…c394
3 touches
1 conflict
0x92f2bafc…f972
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