← previous blocknext block →recent activity
Analyzing
Block #72,497,371
6 transactions · 6 stateful · 2026-05-05 01:55:46 UTC
Parallelism
67/100
Blocked
17%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #72,497,371 · 6 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x3cdea1fa…d9e8
0x065c9d…c394
4 touches
1 conflict
0x67e26bd6…61f1
0x065c9d…c394
3 touches
1 conflict
0x21f20950…c7f2
0x065c9d…c394
3 touches
1 conflict
0xb6213c83…e923
0x065c9d…c394
3 touches
1 conflict
0xc568ea7b…fe33
0x065c9d…c394
3 touches
1 conflict
0x92c9c32d…1847
0x065c9d…c394
2 touches
0 conflicts
0xb1d4f2a1…7c58
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