← previous blocknext block →recent activity

Analyzing

Block #87,595,904

24 transactions · 18 stateful · 2026-07-14 00:53:07 UTC

Parallelism

79/100

Blocked

33%

Avg conflicts / tx

0.58

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #87,595,904  ·  24 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x92385428…6941

0x34b655…2a6f

10 touches
10 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

10 touches
10 conflicts

0x737acb78…fce8

0x34b655…2a6f

6 touches
3 conflicts

0x4f4a7ac3…021c

0x34b655…2a6f

6 touches
3 conflicts

0x4c188934…158e

0x34b655…2a6f

6 touches
3 conflicts

0xe06bbb2e…9416

0x34b655…2a6f

6 touches
3 conflicts

0xe06bbb2e…9417

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

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 0x92385428ad…dc6941

← previous block·next block →recent activity