← previous blocknext block →recent activity

Analyzing

Block #86,980,899

23 transactions · 18 stateful · 2026-07-11 04:19:58 UTC

Parallelism

87/100

Blocked

39%

Avg conflicts / tx

0.35

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #86,980,899  ·  23 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xbcc5ae85…6ba2

0xa6afd3…d132

6 touches
3 conflicts

0xb07a0849…3b62

0xb1dbf0…c0d3

4 touches
1 conflict

0x00000000…003d

0xa6afd3…d132

4 touches
1 conflict

0x33bd5ec4…af53

0xa6afd3…d132

4 touches
1 conflict

0x6a248bdc…3c1b

0xb1dbf0…c0d3

4 touches
1 conflict

0x8a35acfb…d1a9

0xb1dbf0…c0d3

4 touches
1 conflict

0x8a35acfb…d1aa

0xb1dbf0…c0d3

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

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 0xbcc5ae852a…5f6ba2

← previous block·next block →recent activity