← previous blocknext block →recent activity
Analyzing
Block #72,497,764
7 transactions · 7 stateful · 2026-05-05 01:58:22 UTC
Parallelism
71/100
Blocked
29%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #72,497,764 · 7 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
1w02w13w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x00000000…0012
0x1b6862…e19c
4 touches
1 conflict
0x95a141ae…73b6
0x065c9d…c394
4 touches
1 conflict
0x4e0196a0…d2ae
0x065c9d…c394
3 touches
1 conflict
0xaca00e69…534c
0x065c9d…c394
3 touches
1 conflict
0x8c01e20e…c145
0x065c9d…c394
2 touches
0 conflicts
0xbc942767…8edf
0x065c9d…c394
2 touches
0 conflicts
0xd2a00902…2507
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