← previous blocknext block →recent activity

Analyzing

Block #85,680,348

19 transactions · 17 stateful · 2026-07-05 03:33:11 UTC

Parallelism

68/100

Blocked

47%

Avg conflicts / tx

0.95

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #85,680,348  ·  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

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0x8fbde2b3…9b8f

0x34b655…2a6f

8 touches
6 conflicts

0x0aa54240…f89e

0x34b655…2a6f

8 touches
6 conflicts

0x62d6e82b…a750

0x34b655…2a6f

8 touches
6 conflicts

0xcdc1731c…b91a

0x34b655…2a6f

6 touches
3 conflicts

0xedf4636f…b2a2

0x34b655…2a6f

6 touches
3 conflicts

0xe03bbbf2…f240

0x34b655…2a6f

6 touches
3 conflicts

0xb9b4eff6…c3ef

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

15 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity