← previous blocknext block →recent activity
Analyzing
Block #75,532,612
9 transactions · 6 stateful · 2026-05-19 03:34:22 UTC
Parallelism
78/100
Blocked
17%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,532,612 · 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5f77d607…2c84
0x065c9d…c394
4 touches
1 conflict
0xecb46f1f…4b1b
0x065c9d…c394
3 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x3253deba…24f3
0x065c9d…c394
2 touches
0 conflicts
0x443a3e47…f4a4
0x065c9d…c394
2 touches
0 conflicts
0x46280949…b64f
0x065c9d…c394
2 touches
0 conflicts
0x8c10794d…abc5
0x065c9d…c394
2 touches
0 conflicts
0x8e78a93d…8ac0
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 0x5f77d60791…b12c84
Audit this contract →
← previous block·next block →recent activity