← previous blocknext block →recent activity
Analyzing
Block #75,843,332
6 transactions · 5 stateful · 2026-05-20 14:05:56 UTC
Parallelism
50/100
Blocked
40%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #75,843,332 · 6 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
1w02w13w2
- 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
0x057923d1…2c2c
0x065c9d…c394
4 touches
1 conflict
0x3fef21c0…4cb9
0x065c9d…c394
3 touches
1 conflict
0x8cc0f908…9eb8
0x065c9d…c394
2 touches
0 conflicts
0xbf0bcdbf…1cc9
0x065c9d…c394
2 touches
0 conflicts
0xdba12831…56a5
0x065c9d…c394
2 touches
0 conflicts
0x00000000…0012
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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity