← previous blocknext block →recent activity

Analyzing

Block #86,674,618

24 transactions · 18 stateful · 2026-07-09 18:13:24 UTC

Parallelism

71/100

Blocked

39%

Avg conflicts / tx

0.79

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #86,674,618  ·  24 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0x92385428…6941

0x34b655…2a6f

6 touches
3 conflicts

0x56b5f5c0…a3ad

0x34b655…2a6f

6 touches
3 conflicts

0x461428a9…24b3

0x34b655…2a6f

6 touches
3 conflicts

0xb920dba4…4826

0x34b655…2a6f

6 touches
3 conflicts

0xbf6f0703…7aa6

0x34b655…2a6f

6 touches
3 conflicts

0x620b761c…270e

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 0xc824469a90…af6425

← previous block·next block →recent activity