← previous blocknext block →recent activity
Analyzing
Block #75,866,466
12 transactions · 12 stateful · 2026-05-20 16:40:55 UTC
Parallelism
67/100
Blocked
33%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #75,866,466 · 12 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w28w39w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x892daf6e…48d8
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x5f77d607…2c84
0x065c9d…c394
4 touches
1 conflict
0xadc619ae…f2cd
0x065c9d…c394
4 touches
1 conflict
0xa561c19a…1bb8
0x065c9d…c394
3 touches
1 conflict
0x23c0a42f…fdf8
0x065c9d…c394
3 touches
1 conflict
0xbb37dd4b…05ba
0x065c9d…c394
2 touches
0 conflicts
0xcfa4e603…1892
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
3 conflicts on slot 0x892daf6e5d…6d48d8
Audit this contract →
← previous block·next block →recent activity