← previous blocknext block →recent activity

Analyzing

Block #86,485,204

22 transactions · 21 stateful · 2026-07-08 21:05:01 UTC

Parallelism

73/100

Blocked

38%

Avg conflicts / tx

0.59

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #86,485,204  ·  22 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x0e9a70ab…e67c

0x34b655…2a6f

6 touches
3 conflicts

0x3d4584df…ffed

0x34b655…2a6f

6 touches
3 conflicts

0x6637e421…af93

0x34b655…2a6f

6 touches
3 conflicts

0x0ab54c30…b88e

0x34b655…2a6f

6 touches
3 conflicts

0x7ee6007b…fd68

0x34b655…2a6f

6 touches
3 conflicts

0xc948dbdc…199a

0x34b655…2a6f

6 touches
3 conflicts

0xe727ab72…768b

0x34b655…2a6f

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

6 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity