← previous blocknext block →recent activity
Analyzing
Block #75,472,006
19 transactions · 16 stateful · 2026-05-18 20:41:44 UTC
Parallelism
84/100
Blocked
38%
Avg conflicts / tx
0.47
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #75,472,006 · 19 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
4w07w09w010w011w112w213w114w115w218w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xd6b23593…5371
0xd32edf…ff58
5 touches
3 conflicts
0xa17ec269…7cdd
0x1d1325…2305
4 touches
1 conflict
0x12309510…0ac2
0x000000…012a
4 touches
1 conflict
0x99a21305…dffc
0x2a68ba…90c5
4 touches
1 conflict
0x5086c64a…28ba
0x34b655…2a6f
4 touches
1 conflict
0x7a8c7691…77a0
0x34b655…2a6f
4 touches
1 conflict
0x1fff6dcb…b3f4
0xc8689a…ee79
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity