← previous blocknext block →recent activity

Analyzing

Block #75,513,132

33 transactions · 25 stateful · 2026-05-19 01:22:33 UTC

Parallelism

67/100

Blocked

76%

Avg conflicts / tx

1.55

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #75,513,132  ·  33 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others

Conflict graph

Blocked by

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0xe6455d1f…1029

0x754704…b603

12 touches
15 conflicts

0x0d0b2509…074d

0x3bd359…433a

12 touches
15 conflicts

0x0c601f40…69c8

0xd32edf…ff58

11 touches
15 conflicts

0x00000000…0013

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…0015

0x1b6862…e19c

10 touches
10 conflicts

0x1da7723c…80a8

0x1b6862…e19c

10 touches
10 conflicts

0x00000000…0029

0x1b6862…e19c

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

8 touches
6 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: USDC (USDC)

15 conflicts on slot 0xe6455d1fbe…eb1029

← previous block·next block →recent activity