← previous blocknext block →recent activity

Analyzing

Block #87,627,494

24 transactions · 22 stateful · 2026-07-14 04:24:20 UTC

Parallelism

71/100

Blocked

55%

Avg conflicts / tx

1.29

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #87,627,494  ·  24 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x6fe7d366…78ff

0x34b655…2a6f

10 touches
10 conflicts

0x925c118c…a1d8

0x34b655…2a6f

8 touches
6 conflicts

0x18e900fa…07f4

0x34b655…2a6f

6 touches
3 conflicts

0x4c188934…158e

0x34b655…2a6f

6 touches
3 conflicts

0x1175233a…64e7

0x34b655…2a6f

6 touches
3 conflicts

0x11d629eb…bcd9

0x34b655…2a6f

6 touches
3 conflicts

0xc6ed530e…fa7d

0x34b655…2a6f

6 touches
3 conflicts

0xcef0e4b7…46bf

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 0x6fe7d366be…a578ff

← previous block·next block →recent activity