← previous blocknext block →recent activity

Analyzing

Block #87,615,738

21 transactions · 21 stateful · 2026-07-14 03:05:44 UTC

Parallelism

71/100

Blocked

38%

Avg conflicts / tx

0.95

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #87,615,738  ·  21 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

0xc9fe0433…7f01

0x34b655…2a6f

12 touches
15 conflicts

0xd379a368…fea4

0x34b655…2a6f

10 touches
10 conflicts

0xa0af25f7…9129

0x34b655…2a6f

10 touches
10 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

10 touches
10 conflicts

0x25329a48…4e00

0x34b655…2a6f

10 touches
10 conflicts

0x1175233a…64e7

0x34b655…2a6f

10 touches
10 conflicts

0xcef0e4b7…46bf

0x34b655…2a6f

10 touches
10 conflicts

0x5170a218…3a84

0xc8689a…ee79

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

15 conflicts on slot 0xc9fe0433ca…417f01

← previous block·next block →recent activity