← previous blocknext block →recent activity

Analyzing

Block #86,103,656

20 transactions · 18 stateful · 2026-07-07 02:36:26 UTC

Parallelism

85/100

Blocked

39%

Avg conflicts / tx

0.45

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #86,103,656  ·  20 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

0xa19aba84…8922

0xa6afd3…d132

6 touches
3 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x30fa662a…06e0

0x34b655…2a6f

4 touches
1 conflict

0x46b62326…9b3c

0xa6afd3…d132

4 touches
1 conflict

0x65903ef9…2567

0x34b655…2a6f

4 touches
1 conflict

0x8354a485…3642

0x34b655…2a6f

4 touches
1 conflict

0xb91a6f59…722c

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 0xa19aba84c8…5b8922

← previous block·next block →recent activity