← previous blocknext block →recent activity

Analyzing

Block #76,212,031

25 transactions · 22 stateful · 2026-05-22 07:02:11 UTC

Parallelism

56/100

Blocked

55%

Avg conflicts / tx

1.48

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #76,212,031  ·  25 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

0x00000000…003d

0xa6afd3…d132

12 touches
15 conflicts

0xda77597c…92ec

0xd32edf…ff58

11 touches
15 conflicts

0xf282c2b3…28b4

0xa6afd3…d132

10 touches
10 conflicts

0x00000000…0015

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…001f

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…002f

0x1b6862…e19c

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

8 touches
6 conflicts

0xda6b535e…6d6e

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: Kuru Exchange: Market-WETH/USDC

15 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity