← previous blocknext block →recent activity

Analyzing

Block #87,420,670

22 transactions · 20 stateful · 2026-07-13 05:20:26 UTC

Parallelism

64/100

Blocked

50%

Avg conflicts / tx

1.59

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #87,420,670  ·  22 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

0x95c47f03…f1bb

0x34b655…2a6f

14 touches
21 conflicts

0xa15e2d91…025a

0x34b655…2a6f

10 touches
10 conflicts

0xeee4efbb…48c3

0x34b655…2a6f

8 touches
6 conflicts

0x861e5aef…d32c

0x34b655…2a6f

6 touches
3 conflicts

0x0a57a2b8…3cdd

0x34b655…2a6f

6 touches
3 conflicts

0x2099241a…2d2a

0x34b655…2a6f

6 touches
3 conflicts

0x8e8496d5…5beb

0x34b655…2a6f

6 touches
3 conflicts

0x8ebf5869…6785

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

21 conflicts on slot 0x95c47f0322…51f1bb

← previous block·next block →recent activity