← previous blocknext block →recent activity
Analyzing
Block #75,745,233
9 transactions · 8 stateful · 2026-05-20 03:11:59 UTC
Parallelism
78/100
Blocked
38%
Avg conflicts / tx
0.33
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,745,233 · 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
1w02w03w16w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdfa159d0…1576
0x065c9d…c394
4 touches
1 conflict
0xcc4f1f14…aa5f
0x065c9d…c394
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x2347a274…04c4
0x065c9d…c394
2 touches
0 conflicts
0x234d473c…09e5
0x065c9d…c394
2 touches
0 conflicts
0x701612d1…009c
0x065c9d…c394
2 touches
0 conflicts
0xd396e82e…1f05
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 0xdfa159d0ee…971576
Audit this contract →
← previous block·next block →recent activity