← previous blocknext block →recent activity
Analyzing
Block #75,032,441
10 transactions · 7 stateful · 2026-05-16 19:45:06 UTC
Parallelism
80/100
Blocked
14%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,032,441 · 10 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
1w08w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xba38536d…2b7d
0x065c9d…c394
4 touches
1 conflict
0x0c171f0a…4f81
0x065c9d…c394
2 touches
0 conflicts
0x2d1b34a3…d2c8
0x065c9d…c394
2 touches
0 conflicts
0x65df09d6…dbca
0x065c9d…c394
2 touches
0 conflicts
0x93476e49…09ed
0x065c9d…c394
2 touches
0 conflicts
0xa44d6677…c14b
0x065c9d…c394
2 touches
0 conflicts
0xb08e30b1…0b43
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