← previous blocknext block →recent activity

Analyzing

Block #86,704,036

18 transactions · 16 stateful · 2026-07-09 21:29:41 UTC

Parallelism

78/100

Blocked

44%

Avg conflicts / tx

0.5

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,704,036  ·  18 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x9da6e429…074d

0xa6afd3…d132

6 touches
3 conflicts

0xfc578b53…9b1f

0xa6afd3…d132

6 touches
3 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0x1c03f81f…b304

0x34b655…2a6f

4 touches
1 conflict

0x30ded6ec…3424

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x4abfb389…18f4

0x34b655…2a6f

4 touches
1 conflict

0x4fe65078…76b9

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

3 conflicts on slot 0x9da6e42935…3b074d

← previous block·next block →recent activity