← previous blocknext block →recent activity
Analyzing
Block #72,225,554
8 transactions · 5 stateful · 2026-05-03 19:40:51 UTC
Parallelism
75/100
Blocked
20%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #72,225,554 · 8 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
1w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xf70872c7…d5a7
0x065c9d…c394
4 touches
1 conflict
0xfb687a4f…76b6
0x065c9d…c394
3 touches
1 conflict
0xd496c7fb…4c1c
0x065c9d…c394
3 touches
1 conflict
0x458d238c…48de
0x065c9d…c394
2 touches
0 conflicts
0x47b807a2…3307
0x065c9d…c394
2 touches
0 conflicts
0xac5fb230…ef0e
0x065c9d…c394
2 touches
0 conflicts
0xbdf98ce2…9107
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