← previous blocknext block →recent activity
Analyzing
Block #75,701,630
16 transactions · 10 stateful · 2026-05-19 22:21:32 UTC
Parallelism
69/100
Blocked
60%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #75,701,630 · 16 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w28w310w412w415w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9bf064a6…4f04
0x2a68ba…90c5
6 touches
3 conflicts
0x97b5e4e0…456b
0xd32edf…ff58
5 touches
3 conflicts
0xdfa159d0…1576
0x065c9d…c394
4 touches
1 conflict
0xcc4f1f14…aa5f
0x065c9d…c394
4 touches
1 conflict
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0xa5f12fb3…213b
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 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: MarginAccount
3 conflicts on slot 0x9bf064a6f8…394f04
Audit this contract →
← previous block·next block →recent activity