← previous blocknext block →recent activity

Analyzing

Block #84,572,863

50 transactions · 31 stateful · 2026-06-30 00:32:04 UTC

Parallelism

82/100

Blocked

48%

Avg conflicts / tx

0.8

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #84,572,863  ·  50 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0xde2a7317…b0c0

0xd32edf…ff58

11 touches
15 conflicts

0x29686688…0598

0xa6afd3…d132

10 touches
10 conflicts

0x1d2a8430…30bf

0xa6afd3…d132

9 touches
10 conflicts

0xab86573c…682e

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

8 touches
6 conflicts

0x8cf3d245…1d0d

0x69df8a…6292

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