← previous blocknext block →recent activity

Analyzing

Block #85,856,013

23 transactions · 18 stateful · 2026-07-05 23:04:28 UTC

Parallelism

91/100

Blocked

28%

Avg conflicts / tx

0.26

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #85,856,013  ·  23 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

0x33bd5ec4…af53

0xa6afd3…d132

4 touches
1 conflict

0x00ddbbf2…4588

0x34b655…2a6f

4 touches
1 conflict

0x3b9bb58c…e73a

0x34b655…2a6f

4 touches
1 conflict

0x13a54fa2…5ae3

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…003d

0xa6afd3…d132

4 touches
1 conflict

0x9f428a02…c08b

0x065c9d…c394

3 touches
1 conflict

0xf883da2a…23ce

0xd32edf…ff58

3 touches
1 conflict

0x00000000…0002

0x453805…c7fd

2 touches
0 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

1 conflict on slot 0x33bd5ec462…15af53

← previous block·next block →recent activity