← previous blocknext block →recent activity
Analyzing
Block #72,971,608
14 transactions · 12 stateful · 2026-05-07 06:35:32 UTC
Parallelism
71/100
Blocked
33%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #72,971,608 · 14 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w27w28w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xce7bfe5e…5e58
0x065c9d…c394
6 touches
3 conflicts
0xfa5b06d2…51a4
0x065c9d…c394
4 touches
2 conflicts
0xe09eda07…8dda
0x2a68ba…90c5
4 touches
1 conflict
0x0175b7a6…1db9
0x6ca43f…c331
4 touches
1 conflict
0x0175b7a6…1dba
0x6ca43f…c331
4 touches
1 conflict
0x0175b7a6…1dbb
0x6ca43f…c331
4 touches
1 conflict
0x0175b7a6…1dbc
0x6ca43f…c331
4 touches
1 conflict
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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity