← previous blocknext block →recent activity

Analyzing

Block #85,873,953

21 transactions · 18 stateful · 2026-07-06 01:03:49 UTC

Parallelism

86/100

Blocked

33%

Avg conflicts / tx

0.48

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #85,873,953  ·  21 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xee21ba9f…e691

0x34b655…2a6f

6 touches
3 conflicts

0x7aad02c6…b979

0x34b655…2a6f

6 touches
3 conflicts

0xafd867b7…2b2d

0x34b655…2a6f

6 touches
3 conflicts

0xe5bb3628…e5f1

0x34b655…2a6f

6 touches
3 conflicts

0xafd867b7…2b2e

0x34b655…2a6f

6 touches
3 conflicts

0x79e45bd8…5d05

0x34b655…2a6f

4 touches
1 conflict

0x7c0bdc54…9dde

0x34b655…2a6f

4 touches
1 conflict

0x7fa509a2…3ec9

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

3 conflicts on slot 0xee21ba9f5f…61e691

← previous block·next block →recent activity