← previous blocknext block →recent activity
Analyzing
Block #75,123,224
10 transactions · 10 stateful · 2026-05-17 05:50:47 UTC
Parallelism
70/100
Blocked
40%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #75,123,224 · 10 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
1w02w13w04w16w28w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x84d2dd79…2e57
0x065c9d…c394
4 touches
1 conflict
0x765c236f…ff45
0x2a68ba…90c5
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xba38536d…2b7d
0x065c9d…c394
4 touches
1 conflict
0x289c61c6…ceff
0xd32edf…ff58
3 touches
1 conflict
0xbd18e4eb…ae85
0x065c9d…c394
3 touches
1 conflict
0xf348be91…538c
0x065c9d…c394
3 touches
1 conflict
0xb974ae0c…635b
0x065c9d…c394
3 touches
1 conflict
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 0x84d2dd79af…752e57
Audit this contract →
← previous block·next block →recent activity