← previous blocknext block →recent activity

Analyzing

Block #87,718,619

16 transactions · 15 stateful · 2026-07-14 14:33:51 UTC

Parallelism

69/100

Blocked

47%

Avg conflicts / tx

0.94

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #87,718,619  ·  16 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

0x7525206c…fbd5

0x34b655…2a6f

10 touches
10 conflicts

0x5e0b8bbe…377b

0x34b655…2a6f

8 touches
6 conflicts

0x67905f6e…02a1

0x34b655…2a6f

8 touches
6 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

8 touches
6 conflicts

0x5b145de0…367c

0xc8689a…ee79

8 touches
6 conflicts

0xa37210b7…a33f

0x34b655…2a6f

8 touches
6 conflicts

0xeeaba9d3…b491

0x34b655…2a6f

8 touches
6 conflicts

0x13510de3…1c68

0x34b655…2a6f

8 touches
6 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 0x7525206cf5…dcfbd5

← previous block·next block →recent activity