← previous blocknext block →recent activity

Analyzing

Block #87,503,571

19 transactions · 16 stateful · 2026-07-13 14:34:46 UTC

Parallelism

74/100

Blocked

50%

Avg conflicts / tx

0.74

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #87,503,571  ·  19 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x6fe7d366…78ff

0x34b655…2a6f

8 touches
6 conflicts

0x5170a218…3a84

0xc8689a…ee79

6 touches
3 conflicts

0x92385428…6941

0x34b655…2a6f

6 touches
3 conflicts

0x94d707b6…7c4e

0x34b655…2a6f

6 touches
3 conflicts

0x951ffdff…8e9f

0x34b655…2a6f

6 touches
3 conflicts

0xa4bee7a4…ff14

0x34b655…2a6f

6 touches
3 conflicts

0xbe179c31…8fdb

0x34b655…2a6f

6 touches
3 conflicts

0x286711a5…b3bf

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 0x6fe7d366be…a578ff

← previous block·next block →recent activity