← previous blocknext block →recent activity

Analyzing

Block #86,755,072

24 transactions · 22 stateful · 2026-07-10 03:10:46 UTC

Parallelism

83/100

Blocked

27%

Avg conflicts / tx

0.5

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,755,072  ·  24 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

8 touches
6 conflicts

0xe283e878…7262

0x34b655…2a6f

6 touches
3 conflicts

0x4e66a473…9fe8

0x34b655…2a6f

6 touches
3 conflicts

0x7efe7298…f6db

0x34b655…2a6f

6 touches
3 conflicts

0x818b0b44…ff6f

0x34b655…2a6f

6 touches
3 conflicts

0x92385428…6941

0x34b655…2a6f

6 touches
3 conflicts

0xab98deda…aec3

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 0x482471adbb…39122f

← previous block·next block →recent activity