← previous blocknext block →recent activity

Analyzing

Block #86,621,845

23 transactions · 19 stateful · 2026-07-09 12:19:40 UTC

Parallelism

78/100

Blocked

42%

Avg conflicts / tx

0.74

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #86,621,845  ·  23 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xfaef08b1…0696

0x34b655…2a6f

10 touches
10 conflicts

0xfceed1d1…d745

0xd32edf…ff58

7 touches
6 conflicts

0x8a35acfb…d1ab

0xb1dbf0…c0d3

7 touches
6 conflicts

0x00000000…002f

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0004

0xb1dbf0…c0d3

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0012

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 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: Perpl

10 conflicts on slot 0xfaef08b108…f90696

← previous block·next block →recent activity