← previous blocknext block →recent activity

Analyzing

Block #86,630,912

26 transactions · 24 stateful · 2026-07-09 13:20:12 UTC

Parallelism

62/100

Blocked

54%

Avg conflicts / tx

1.27

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #86,630,912  ·  26 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0xfaef08b1…0696

0x34b655…2a6f

14 touches
21 conflicts

0x347327ff…3863

0x34b655…2a6f

8 touches
6 conflicts

0x90e113f8…c8f9

0xc8689a…ee79

8 touches
6 conflicts

0x4caf91f9…8ab5

0x34b655…2a6f

8 touches
6 conflicts

0xfa2527aa…9dd5

0x34b655…2a6f

8 touches
6 conflicts

0xa7013be2…c0a8

0x34b655…2a6f

8 touches
6 conflicts

0xfe3d37ee…6e67

0x34b655…2a6f

8 touches
6 conflicts

0x1941b441…5889

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

21 conflicts on slot 0xfaef08b108…f90696

← previous block·next block →recent activity