← previous blocknext block →recent activity
Analyzing
Block #75,701,850
9 transactions · 8 stateful · 2026-05-19 22:23:00 UTC
Parallelism
67/100
Blocked
25%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #75,701,850 · 9 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
1w02w14w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xcc4f1f14…aa5f
0x065c9d…c394
4 touches
1 conflict
0xdfa159d0…1576
0x065c9d…c394
4 touches
1 conflict
0xe191ddd3…a236
0x065c9d…c394
3 touches
1 conflict
0x77ca723a…891b
0x065c9d…c394
2 touches
0 conflicts
0x7c8afc15…6fbd
0x065c9d…c394
2 touches
0 conflicts
0x7ff1e8f4…5912
0x065c9d…c394
2 touches
0 conflicts
0xcc727a9b…e7ed
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity