← previous blocknext block →recent activity

Analyzing

Block #87,627,896

22 transactions · 21 stateful · 2026-07-14 04:27:03 UTC

Parallelism

55/100

Blocked

57%

Avg conflicts / tx

1.95

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #87,627,896  ·  22 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0x08330b36…ae29

0x34b655…2a6f

14 touches
21 conflicts

0x49f75237…44f4

0x34b655…2a6f

12 touches
15 conflicts

0x2fade833…5de4

0x34b655…2a6f

10 touches
10 conflicts

0x5b145de0…367c

0xc8689a…ee79

10 touches
10 conflicts

0x13510de3…1c68

0x34b655…2a6f

10 touches
10 conflicts

0x167de262…f61f

0x34b655…2a6f

10 touches
10 conflicts

0x5e0b8bbe…377b

0x34b655…2a6f

10 touches
10 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