← previous blocknext block →recent activity

Analyzing

Block #85,146,346

19 transactions · 18 stateful · 2026-07-02 16:17:14 UTC

Parallelism

68/100

Blocked

39%

Avg conflicts / tx

0.95

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #85,146,346  ·  19 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

0x22e0cc1d…ad0d

0x34b655…2a6f

10 touches
10 conflicts

0x355cda6e…eef8

0x34b655…2a6f

8 touches
6 conflicts

0x3fde350e…8d43

0x34b655…2a6f

8 touches
6 conflicts

0x5f8acc70…8c84

0x34b655…2a6f

8 touches
6 conflicts

0x7204a5b8…b1d5

0x34b655…2a6f

8 touches
6 conflicts

0x9966da31…0d0f

0x34b655…2a6f

8 touches
6 conflicts

0xc99e7125…81b1

0x34b655…2a6f

8 touches
6 conflicts

0xcfa965cc…6fcf

0x34b655…2a6f

8 touches
6 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 0x22e0cc1d4a…90ad0d

← previous block·next block →recent activity