← previous blocknext block →recent activity
Analyzing
Block #75,199,189
9 transactions · 7 stateful · 2026-05-17 14:17:57 UTC
Parallelism
78/100
Blocked
14%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,199,189 · 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
1w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x40934bfc…ce33
0x065c9d…c394
4 touches
1 conflict
0xfce6d8e7…f441
0x065c9d…c394
3 touches
1 conflict
0x275d9f58…013c
0x065c9d…c394
3 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x348fda08…7e96
0x065c9d…c394
2 touches
0 conflicts
0x715f44c8…2e36
0x065c9d…c394
2 touches
0 conflicts
0xf8e1ddfc…20fd
0x065c9d…c394
2 touches
0 conflicts
0x046a928e…0012
0x2a68ba…90c5
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 0x40934bfca8…80ce33
Audit this contract →
← previous block·next block →recent activity