← previous blocknext block →recent activity

Analyzing

Block #85,805,922

22 transactions · 19 stateful · 2026-07-05 17:30:48 UTC

Parallelism

82/100

Blocked

37%

Avg conflicts / tx

0.5

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #85,805,922  ·  22 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

0x00000000…003d

0xa6afd3…d132

8 touches
6 conflicts

0x46b62326…9b3c

0xa6afd3…d132

8 touches
6 conflicts

0xa19aba84…8922

0xa6afd3…d132

6 touches
3 conflicts

0x00000000…0002

0x04fdea…47d7

6 touches
3 conflicts

0x3a15404b…10b1

0x34b655…2a6f

4 touches
1 conflict

0x9385d07d…4829

0x34b655…2a6f

4 touches
1 conflict

0xcc6e2e88…6569

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

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

6 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity