← previous blocknext block →recent activity

Analyzing

Block #85,168,767

20 transactions · 18 stateful · 2026-07-02 18:46:27 UTC

Parallelism

70/100

Blocked

56%

Avg conflicts / tx

0.9

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #85,168,767  ·  20 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

0x7c0bdc54…9dde

0x34b655…2a6f

8 touches
6 conflicts

0xa1144aa9…7f67

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xc83310b1…c778

0x34b655…2a6f

8 touches
6 conflicts

0xffb8950c…23c6

0x34b655…2a6f

8 touches
6 conflicts

0x922c7ebd…6600

0xc8689a…ee79

8 touches
6 conflicts

0xfaef08b1…0696

0x34b655…2a6f

8 touches
6 conflicts

0xd25a34fd…3e4d

0x34b655…2a6f

7 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

6 conflicts on slot 0x7c0bdc5473…099dde

← previous block·next block →recent activity