← previous blocknext block →recent activity

Analyzing

Block #87,725,326

28 transactions · 24 stateful · 2026-07-14 15:18:42 UTC

Parallelism

61/100

Blocked

46%

Avg conflicts / tx

1.29

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #87,725,326  ·  28 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

14 touches
21 conflicts

0xc4de6652…13f4

0x34b655…2a6f

10 touches
10 conflicts

0x28c62bca…b746

0x34b655…2a6f

6 touches
3 conflicts

0x5b145de0…367c

0xc8689a…ee79

6 touches
3 conflicts

0x0dd44476…ef40

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x67905f6e…02a1

0x34b655…2a6f

6 touches
3 conflicts

0x9ae859db…2d84

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

← previous block·next block →recent activity