← previous blocknext block →recent activity

Analyzing

Block #87,497,480

24 transactions · 18 stateful · 2026-07-13 13:54:01 UTC

Parallelism

71/100

Blocked

44%

Avg conflicts / tx

0.71

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #87,497,480  ·  24 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x0da39371…1ecd

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x0733be30…112f

0x34b655…2a6f

6 touches
3 conflicts

0x372b71e7…268c

0x34b655…2a6f

6 touches
3 conflicts

0xab981df1…2941

0x34b655…2a6f

6 touches
3 conflicts

0xc36fa358…24cb

0x34b655…2a6f

6 touches
3 conflicts

0xcfcb8911…e9da

0x34b655…2a6f

6 touches
3 conflicts

0x4c188934…158e

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

6 conflicts on slot 0x0da3937156…891ecd

← previous block·next block →recent activity