← previous blocknext block →recent activity
Analyzing
Block #74,025,297
6 transactions · 5 stateful · 2026-05-12 03:46:10 UTC
Parallelism
67/100
Blocked
20%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,025,297 · 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
1w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9c8c9939…2fb3
0x065c9d…c394
4 touches
1 conflict
0x0b390c61…dc07
0x065c9d…c394
4 touches
1 conflict
0x0fc52f94…2cfd
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x65200699…84d8
0x065c9d…c394
2 touches
0 conflicts
0xde661f90…d30a
0x065c9d…c394
2 touches
0 conflicts
0xe9b9fa70…b2a8
0x065c9d…c394
2 touches
0 conflicts
0xf069fc08…482b
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 0x9c8c9939fd…f62fb3
Audit this contract →
← previous block·next block →recent activity