← previous blocknext block →recent activity

Analyzing

Block #86,154,916

28 transactions · 19 stateful · 2026-07-07 08:18:42 UTC

Parallelism

79/100

Blocked

47%

Avg conflicts / tx

0.71

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #86,154,916  ·  28 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

0x89750670…2dea

0xa6afd3…d132

10 touches
10 conflicts

0x00000000…003d

0xa6afd3…d132

10 touches
10 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

10 touches
10 conflicts

0xb4c35fcd…43ae

0xa6afd3…d132

10 touches
10 conflicts

0xdf708ee7…1fcf

0xc8689a…ee79

8 touches
6 conflicts

0xef65bff3…7c9d

0x2a68ba…90c5

8 touches
6 conflicts

0x40970e69…da50

0x69df8a…6292

8 touches
6 conflicts

0x8cf3d245…1d0d

0x69df8a…6292

8 touches
6 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

10 conflicts on slot 0x89750670de…b02dea

← previous block·next block →recent activity