← previous blocknext block →recent activity

Analyzing

Block #86,737,861

24 transactions · 20 stateful · 2026-07-10 01:15:39 UTC

Parallelism

75/100

Blocked

45%

Avg conflicts / tx

0.75

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #86,737,861  ·  24 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

0x0733be30…112f

0x34b655…2a6f

10 touches
10 conflicts

0x56b5f5c0…a3ad

0x34b655…2a6f

10 touches
10 conflicts

0x8267cc91…78bc

0x34b655…2a6f

8 touches
6 conflicts

0xf23e15be…1749

0x34b655…2a6f

8 touches
6 conflicts

0x92385428…6941

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4ab

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xfaef08b1…0696

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 0x0733be30d6…38112f

← previous block·next block →recent activity