← previous blocknext block →recent activity
Analyzing
Block #75,511,918
18 transactions · 13 stateful · 2026-05-19 01:14:15 UTC
Parallelism
78/100
Blocked
46%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #75,511,918 · 18 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w38w010w011w112w217w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x443a3e47…f4a4
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0xd5b10148…e632
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0xbe35594b…0897
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0029
0x1b6862…e19c
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x046a928e…0012
0x2a68ba…90c5
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: Market-MON/USDC
3 conflicts on slot 0x443a3e479f…3af4a4
Audit this contract →
← previous block·next block →recent activity