← previous blocknext block →recent activity
Analyzing
Block #75,903,016
16 transactions · 16 stateful · 2026-05-20 20:44:10 UTC
Parallelism
63/100
Blocked
50%
Avg conflicts / tx
0.94
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #75,903,016 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w39w410w513w014w115w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xf708a304…bdc8
0xd32edf…ff58
7 touches
6 conflicts
0x5f77d607…2c84
0x065c9d…c394
6 touches
3 conflicts
0xcad937e9…786c
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x5086c64a…28ba
0x34b655…2a6f
6 touches
3 conflicts
0x7cee1be1…e770
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity