← previous blocknext block →recent activity

Analyzing

Block #87,622,528

21 transactions · 18 stateful · 2026-07-14 03:51:06 UTC

Parallelism

38/100

Blocked

78%

Avg conflicts / tx

2.24

Longest chain

13 deep

Execution timeline

did this block parallelize well?

view

block #87,622,528  ·  21 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

0x22e0cc1d…ad0d

0x34b655…2a6f

16 touches
28 conflicts

0x79e62da8…efdc

0x34b655…2a6f

14 touches
21 conflicts

0x925c118c…a1d8

0x34b655…2a6f

12 touches
15 conflicts

0x25329a48…4e00

0x34b655…2a6f

10 touches
10 conflicts

0x5170a218…3a84

0xc8689a…ee79

10 touches
10 conflicts

0x1175233a…64e7

0x34b655…2a6f

10 touches
10 conflicts

0x18e900fa…07f4

0x34b655…2a6f

10 touches
10 conflicts

0x68b75835…d6f3

0x34b655…2a6f

10 touches
10 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 0x22e0cc1d4a…90ad0d

← previous block·next block →recent activity