← previous blocknext block →recent activity
Analyzing
Block #75,893,315
11 transactions · 10 stateful · 2026-05-20 19:39:38 UTC
Parallelism
82/100
Blocked
20%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #75,893,315 · 11 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
1w06w19w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x158dfcaa…2370
0x065c9d…c394
2 touches
0 conflicts
0x3b06469d…715e
0x065c9d…c394
2 touches
0 conflicts
0x6f195ce6…b6e8
0x065c9d…c394
2 touches
0 conflicts
0x8355fb0b…8526
0x065c9d…c394
2 touches
0 conflicts
0xa9cc019b…9dcc
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity