← previous blocknext block →recent activity

Analyzing

Block #86,776,277

19 transactions · 17 stateful · 2026-07-10 05:32:19 UTC

Parallelism

74/100

Blocked

47%

Avg conflicts / tx

0.95

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #86,776,277  ·  19 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

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0x482471ad…122f

0x34b655…2a6f

10 touches
10 conflicts

0x1c7f2eca…cf5e

0x34b655…2a6f

8 touches
6 conflicts

0x4984f7be…d515

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0xdf64e5e6…75e8

0x34b655…2a6f

6 touches
3 conflicts

0x1c03f81f…b303

0x34b655…2a6f

6 touches
3 conflicts

0x0733be30…112f

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

10 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity