← previous blocknext block →recent activity
Analyzing
Block #75,505,564
22 transactions · 22 stateful · 2026-05-19 00:30:39 UTC
Parallelism
82/100
Blocked
41%
Avg conflicts / tx
0.77
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #75,505,564 · 22 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
1w02w13w27w08w111w013w014w115w217w318w320w121w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x443a3e47…f4a4
0x065c9d…c394
8 touches
6 conflicts
0xfcb7b8b2…ebb3
0x065c9d…c394
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0xcb45d9d6…cb81
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0019
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
0x1b6862…e19c
6 touches
3 conflicts
0x0d622e34…0000
0x681e90…ae09
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 0x443a3e479f…3af4a4
Audit this contract →
← previous block·next block →recent activity