← previous blocknext block →recent activity

Analyzing

Block #87,587,286

20 transactions · 19 stateful · 2026-07-13 23:55:27 UTC

Parallelism

55/100

Blocked

53%

Avg conflicts / tx

1.15

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #87,587,286  ·  20 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x212c5b04…5f01

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

8 touches
6 conflicts

0xe1a1a29a…a398

0x34b655…2a6f

6 touches
3 conflicts

0xe1a1a29a…a399

0x34b655…2a6f

6 touches
3 conflicts

0xe9452241…95a3

0x34b655…2a6f

6 touches
3 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0x0733be30…112f

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 0x212c5b0431…f85f01

← previous block·next block →recent activity