← previous blocknext block →recent activity

Analyzing

Block #81,479,036

24 transactions · 19 stateful · 2026-06-15 16:26:47 UTC

Parallelism

75/100

Blocked

37%

Avg conflicts / tx

0.58

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #81,479,036  ·  24 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

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0x1d44909b…e905

0xa6afd3…d132

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0xd7a3d42d…e766

0x40c49f…2af0

6 touches
3 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0x00000000…0018

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0028

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0xdb95e18e…c737

0x1b6862…e19c

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-WETH/USDC

3 conflicts on slot 0x1d44909b2f…63e905

← previous block·next block →recent activity