← previous blocknext block →recent activity

Analyzing

Block #86,854,851

19 transactions · 18 stateful · 2026-07-10 14:17:27 UTC

Parallelism

68/100

Blocked

44%

Avg conflicts / tx

1

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #86,854,851  ·  19 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

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0x33b4c2ba…961a

0x34b655…2a6f

4 touches
1 conflict

0x3550075a…fb0f

0x34b655…2a6f

4 touches
1 conflict

0x49af9bda…cb3c

0x34b655…2a6f

4 touches
1 conflict

0x4c214bb3…c5d3

0x34b655…2a6f

4 touches
1 conflict

0x5970f8ee…184d

0x34b655…2a6f

4 touches
1 conflict

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity