← previous blocknext block →recent activity

Analyzing

Block #87,577,432

31 transactions · 29 stateful · 2026-07-13 22:49:33 UTC

Parallelism

58/100

Blocked

45%

Avg conflicts / tx

1.65

Longest chain

13 deep

Execution timeline

did this block parallelize well?

view

block #87,577,432  ·  31 txs across 13 waves  ·  depth 13
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

wave w12

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

0xd98b3c10…67b8

0x34b655…2a6f

16 touches
28 conflicts

0xc36fa358…24cb

0x34b655…2a6f

10 touches
10 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

8 touches
6 conflicts

0x2b5101ac…090b

0x34b655…2a6f

8 touches
6 conflicts

0x5e7da795…a150

0x34b655…2a6f

8 touches
6 conflicts

0x0733be30…112f

0x34b655…2a6f

6 touches
3 conflicts

0x1a5d321d…a474

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4ab

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

28 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity