← previous blocknext block →recent activity

Analyzing

Block #86,884,264

20 transactions · 17 stateful · 2026-07-10 17:34:15 UTC

Parallelism

85/100

Blocked

41%

Avg conflicts / tx

0.45

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #86,884,264  ·  20 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

0xaa48195d…ffee

0x34b655…2a6f

6 touches
3 conflicts

0xb0bc3bf8…e2b1

0x34b655…2a6f

6 touches
3 conflicts

0xb90a53d8…8cae

0x34b655…2a6f

6 touches
3 conflicts

0xedcf2991…8551

0x34b655…2a6f

6 touches
3 conflicts

0xfaef08b1…0696

0x34b655…2a6f

6 touches
3 conflicts

0x922c7ebd…6600

0xc8689a…ee79

6 touches
3 conflicts

0x288bc578…318e

0x34b655…2a6f

6 touches
3 conflicts

0x4327afd2…1b3a

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

3 conflicts on slot 0xaa48195d9c…daffee

← previous block·next block →recent activity