← previous blocknext block →recent activity

Analyzing

Block #87,625,771

28 transactions · 24 stateful · 2026-07-14 04:12:48 UTC

Parallelism

71/100

Blocked

50%

Avg conflicts / tx

1.46

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #87,625,771  ·  28 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

0x00000000…00c9

0x34b655…2a6f

14 touches
21 conflicts

0xac61d3a4…7da8

0x34b655…2a6f

14 touches
21 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

14 touches
21 conflicts

0x18e900fa…07f4

0x34b655…2a6f

12 touches
15 conflicts

0x22e0cc1d…ad07

0x34b655…2a6f

12 touches
15 conflicts

0x4203ff9b…38e2

0x34b655…2a6f

12 touches
15 conflicts

0x5170a218…3a84

0xc8689a…ee79

12 touches
15 conflicts

0x10b7971b…3ba4

0x34b655…2a6f

12 touches
15 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 0x0000000000…0000c9

← previous block·next block →recent activity