← previous blocknext block →recent activity

Analyzing

Block #86,341,316

14 transactions · 10 stateful · 2026-07-08 05:03:22 UTC

Parallelism

79/100

Blocked

40%

Avg conflicts / tx

0.29

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #86,341,316  ·  14 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

0x00000000…003d

0xa6afd3…d132

4 touches
1 conflict

0x5e782d17…5317

0x34b655…2a6f

4 touches
1 conflict

0x5e782d17…5318

0x34b655…2a6f

4 touches
1 conflict

0x67717220…db87

0x34b655…2a6f

4 touches
1 conflict

0xc6f4f168…765c

0x34b655…2a6f

4 touches
1 conflict

0xda46a376…f6a6

0x34b655…2a6f

4 touches
1 conflict

0xfefb0189…f726

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x40c49f…2af0

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

1 conflict on slot 0x0000000000…00003d

← previous block·next block →recent activity