← previous blocknext block →recent activity
Analyzing
Block #75,525,696
17 transactions · 12 stateful · 2026-05-19 02:48:29 UTC
Parallelism
88/100
Blocked
33%
Avg conflicts / tx
0.24
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,525,696 · 17 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
1w02w03w15w17w011w115w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x892daf6e…48d8
0x065c9d…c394
4 touches
1 conflict
0x5086c64a…28ba
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x08a79387…f87a
0xd32edf…ff58
3 touches
1 conflict
0x5716fac1…5d83
0x065c9d…c394
2 touches
0 conflicts
0x9048e834…d366
0x065c9d…c394
2 touches
0 conflicts
0xb962f7c1…0d8a
0x065c9d…c394
2 touches
0 conflicts
0xfed971c0…39bf
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 0x892daf6e5d…6d48d8
Audit this contract →
← previous block·next block →recent activity