← previous blocknext block →recent activity

Analyzing

Block #86,711,054

21 transactions · 17 stateful · 2026-07-09 22:16:29 UTC

Parallelism

90/100

Blocked

29%

Avg conflicts / tx

0.24

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #86,711,054  ·  21 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

4 touches
1 conflict

0x0733be30…112f

0x34b655…2a6f

4 touches
1 conflict

0x75854a6e…5d6d

0x34b655…2a6f

4 touches
1 conflict

0x75854a6e…5d6e

0x34b655…2a6f

4 touches
1 conflict

0xcfb9b777…5e1b

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xdd805c08…e0e1

0x34b655…2a6f

4 touches
1 conflict

0xf23e15be…1749

0x34b655…2a6f

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

1 conflict on slot 0xfc578b53da…c79b1f

← previous block·next block →recent activity