← previous blocknext block →recent activity

Analyzing

Block #86,272,344

33 transactions · 24 stateful · 2026-07-07 21:22:44 UTC

Parallelism

70/100

Blocked

42%

Avg conflicts / tx

1.06

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #86,272,344  ·  33 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

0xd98b3c10…67b8

0x34b655…2a6f

16 touches
28 conflicts

0x96dd83e6…a507

0x34b655…2a6f

12 touches
15 conflicts

0xec63e4f6…4778

0x34b655…2a6f

10 touches
10 conflicts

0xe5bb3628…e5f1

0x34b655…2a6f

10 touches
10 conflicts

0x7aad02c6…b979

0x34b655…2a6f

8 touches
6 conflicts

0x99479bc5…3a88

0x34b655…2a6f

6 touches
3 conflicts

0x0817711c…bf1f

0x34b655…2a6f

6 touches
3 conflicts

0xb5cddf91…0abf

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

28 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity