← previous blocknext block →recent activity

Analyzing

Block #87,735,270

22 transactions · 21 stateful · 2026-07-14 16:25:14 UTC

Parallelism

73/100

Blocked

43%

Avg conflicts / tx

1.14

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #87,735,270  ·  22 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x0733be30…112f

0x34b655…2a6f

12 touches
15 conflicts

0xbc94dfe1…0b3d

0x34b655…2a6f

10 touches
10 conflicts

0x9001f549…089d

0x34b655…2a6f

10 touches
10 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

10 touches
10 conflicts

0x5b145de0…367c

0xc8689a…ee79

8 touches
6 conflicts

0x077d58c3…8ed7

0x34b655…2a6f

8 touches
6 conflicts

0x22e7ebfe…1293

0x34b655…2a6f

8 touches
6 conflicts

0x26050074…6967

0x34b655…2a6f

8 touches
6 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

15 conflicts on slot 0x0733be30d6…38112f

← previous block·next block →recent activity