← previous blocknext block →recent activity
Analyzing
Block #72,570,967
7 transactions · 7 stateful · 2026-05-05 10:05:46 UTC
Parallelism
57/100
Blocked
29%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #72,570,967 · 7 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x30563bd8…1af3
0x065c9d…c394
4 touches
1 conflict
0x2cc13fdc…84a8
0x065c9d…c394
3 touches
1 conflict
0xe74174fa…64fc
0x065c9d…c394
3 touches
1 conflict
0x673b494e…6011
0x065c9d…c394
2 touches
0 conflicts
0x69e3e690…00f6
0x065c9d…c394
2 touches
0 conflicts
0x9c516f73…20aa
0x065c9d…c394
2 touches
0 conflicts
0xd445ad84…a727
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity