← previous blocknext block →recent activity
Analyzing
Block #75,731,626
9 transactions · 9 stateful · 2026-05-20 01:41:24 UTC
Parallelism
78/100
Blocked
11%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,731,626 · 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
2w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x54af6a2a…82b6
0x065c9d…c394
3 touches
1 conflict
0x23f10095…f5c3
0x065c9d…c394
3 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x2f88a23f…9dc5
0x2a68ba…90c5
2 touches
0 conflicts
0x1a356d76…6c74
0x34b655…2a6f
2 touches
0 conflicts
0x4ec9ff52…e6f7
0x34b655…2a6f
2 touches
0 conflicts
0x5b6af007…0f35
0x34b655…2a6f
2 touches
0 conflicts
0x89999c15…fdac
0x34b655…2a6f
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 0x54af6a2aa5…0582b6
Audit this contract →
← previous block·next block →recent activity