← previous blocknext block →recent activity

Analyzing

Block #87,409,623

22 transactions · 22 stateful · 2026-07-13 04:06:32 UTC

Parallelism

77/100

Blocked

41%

Avg conflicts / tx

0.91

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #87,409,623  ·  22 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

0x4cabb80a…46bf

0x34b655…2a6f

10 touches
10 conflicts

0xa099602a…7731

0x34b655…2a6f

8 touches
6 conflicts

0x00842ba8…bdc6

0x34b655…2a6f

6 touches
3 conflicts

0x0eeb2a30…6909

0x34b655…2a6f

6 touches
3 conflicts

0x67d02b69…3795

0x34b655…2a6f

6 touches
3 conflicts

0x734ee320…caae

0x34b655…2a6f

6 touches
3 conflicts

0x85c84f98…06d7

0x34b655…2a6f

6 touches
3 conflicts

0x8bf661cb…bcd2

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

10 conflicts on slot 0x4cabb80a0e…7546bf

← previous block·next block →recent activity