← previous blocknext block →recent activity

Analyzing

Block #87,579,602

26 transactions · 20 stateful · 2026-07-13 23:04:04 UTC

Parallelism

69/100

Blocked

50%

Avg conflicts / tx

1.15

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #87,579,602  ·  26 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x2d651956…12e8

0x34b655…2a6f

10 touches
10 conflicts

0xdb7c435f…f490

0x34b655…2a6f

8 touches
6 conflicts

0x4cfbc6b1…2649

0x34b655…2a6f

8 touches
6 conflicts

0x882d467b…97d6

0x34b655…2a6f

8 touches
6 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

8 touches
6 conflicts

0x57998639…d04d

0x34b655…2a6f

8 touches
6 conflicts

0xff7d5fa4…6ea6

0x34b655…2a6f

6 touches
3 conflicts

0x41bc5f7b…26f2

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

10 conflicts on slot 0x2d65195682…4112e8

← previous block·next block →recent activity