← previous blocknext block →recent activity
Analyzing
Block #72,398,956
17 transactions · 11 stateful · 2026-05-04 15:00:15 UTC
Parallelism
88/100
Blocked
9%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #72,398,956 · 17 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
1w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xe8fd8dc3…7ef5
0x065c9d…c394
4 touches
1 conflict
0x9702875d…a369
0x065c9d…c394
3 touches
1 conflict
0xa5d787da…c111
0x065c9d…c394
3 touches
1 conflict
0x2e7900e0…254b
0x065c9d…c394
2 touches
0 conflicts
0xb925ec0a…031f
0x065c9d…c394
2 touches
0 conflicts
0xd4e962f8…5d60
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
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