← previous blocknext block →recent activity

Analyzing

Block #86,351,474

23 transactions · 19 stateful · 2026-07-08 06:11:08 UTC

Parallelism

74/100

Blocked

42%

Avg conflicts / tx

0.52

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #86,351,474  ·  23 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

0xfc578b53…9b1f

0xa6afd3…d132

8 touches
6 conflicts

0x00000000…003d

0xa6afd3…d132

8 touches
6 conflicts

0x112cf8ad…6e4f

0xa6afd3…d132

8 touches
6 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x40c49f…2af0

4 touches
1 conflict

0xae5e6f9a…2991

0xc8689a…ee79

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

6 conflicts on slot 0xfc578b53da…c79b1f

← previous block·next block →recent activity