← previous blocknext block →recent activity

Analyzing

Block #87,699,055

21 transactions · 20 stateful · 2026-07-14 12:22:34 UTC

Parallelism

62/100

Blocked

45%

Avg conflicts / tx

1.43

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #87,699,055  ·  21 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

0x6fe7d366…78ff

0x34b655…2a6f

14 touches
21 conflicts

0x5170a218…3a84

0xc8689a…ee79

8 touches
6 conflicts

0x2fdfa032…139c

0x34b655…2a6f

8 touches
6 conflicts

0xdbb43016…7cc4

0x34b655…2a6f

8 touches
6 conflicts

0xf324b405…ca30

0x34b655…2a6f

8 touches
6 conflicts

0xca18c58e…cede

0x34b655…2a6f

8 touches
6 conflicts

0x0f068b13…fb19

0x34b655…2a6f

8 touches
6 conflicts

0x9e7b589f…fa0c

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