← previous blocknext block →recent activity
Analyzing
Block #75,427,030
11 transactions · 8 stateful · 2026-05-18 15:42:22 UTC
Parallelism
73/100
Blocked
25%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #75,427,030 · 11 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xf4fb515c…9284
0xd32edf…ff58
3 touches
1 conflict
0x2278b510…2725
0x065c9d…c394
2 touches
0 conflicts
0x3ada6e0f…e1b5
0x065c9d…c394
2 touches
0 conflicts
0x3cc73ef5…296f
0x065c9d…c394
2 touches
0 conflicts
0x9c3ea5f8…5d91
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…0013
0x1b6862…e19c
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity