← previous blocknext block →recent activity
Analyzing
Block #74,437,039
9 transactions · 7 stateful · 2026-05-14 01:25:14 UTC
Parallelism
78/100
Blocked
14%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #74,437,039 · 9 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
2w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x751eb745…29ff
0x065c9d…c394
4 touches
1 conflict
0xff6e57a5…fec3
0x065c9d…c394
3 touches
1 conflict
0x48c859a8…d873
0x065c9d…c394
3 touches
1 conflict
0x335a161d…fe7f
0x000000…012a
2 touches
0 conflicts
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x1c6f8b9b…8068
0x065c9d…c394
2 touches
0 conflicts
0x43e085ac…2b6a
0x065c9d…c394
2 touches
0 conflicts
0x6c6b2630…ddb3
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 0x751eb74502…7d29ff
Audit this contract →
← previous block·next block →recent activity