← previous blocknext block →recent activity

Analyzing

Block #87,793,555

21 transactions · 20 stateful · 2026-07-14 22:55:08 UTC

Parallelism

71/100

Blocked

45%

Avg conflicts / tx

1

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #87,793,555  ·  21 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x9465204c…bf37

0x34b655…2a6f

10 touches
10 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

10 touches
10 conflicts

0xd8675136…9a01

0x34b655…2a6f

8 touches
6 conflicts

0x28c62bca…b746

0x34b655…2a6f

8 touches
6 conflicts

0xe5bb3628…e5f1

0x34b655…2a6f

8 touches
6 conflicts

0x2dfde2ed…8801

0x34b655…2a6f

7 touches
6 conflicts

0x5b145de0…367c

0xc8689a…ee79

6 touches
3 conflicts

0x482471ad…122f

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 0x9465204cd8…debf37

← previous block·next block →recent activity