← previous blocknext block →recent activity

Analyzing

Block #86,167,471

33 transactions · 20 stateful · 2026-07-07 09:42:27 UTC

Parallelism

88/100

Blocked

35%

Avg conflicts / tx

0.27

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,167,471  ·  33 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

6 touches
3 conflicts

0x46b62326…9b3c

0xa6afd3…d132

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

4 touches
1 conflict

0xef65bff3…7c9d

0x2a68ba…90c5

4 touches
1 conflict

0x172b0de5…980b

0x34b655…2a6f

4 touches
1 conflict

0x39423b28…1e57

0x34b655…2a6f

4 touches
1 conflict

0x427d1120…4eb1

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 0x0000000000…00003d

← previous block·next block →recent activity