← previous blocknext block →recent activity

Analyzing

Block #86,764,704

25 transactions · 21 stateful · 2026-07-10 04:15:02 UTC

Parallelism

76/100

Blocked

38%

Avg conflicts / tx

1

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #86,764,704  ·  25 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

0xec7fe04a…3c56

0x34b655…2a6f

12 touches
15 conflicts

0xd2771e4d…705d

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xdb3937e8…23cb

0x34b655…2a6f

6 touches
3 conflicts

0x8344e533…436c

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xfaef08b1…0696

0x34b655…2a6f

6 touches
3 conflicts

0x4cdf55e1…0f2d

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

15 conflicts on slot 0xec7fe04ad1…2d3c56

← previous block·next block →recent activity