← previous blocknext block →recent activity

Analyzing

Block #87,330,803

19 transactions · 19 stateful · 2026-07-12 19:19:24 UTC

Parallelism

79/100

Blocked

37%

Avg conflicts / tx

0.53

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #87,330,803  ·  19 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x34443913…cbf3

0x336ed4…c59c

6 touches
3 conflicts

0x47d4745e…02bb

0x336ed4…c59c

6 touches
3 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0x567bb003…113a

0x34b655…2a6f

6 touches
3 conflicts

0x9f287382…28e5

0x34b655…2a6f

6 touches
3 conflicts

0xc0124edf…7d30

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…000a

0x90c374…be45

6 touches
3 conflicts

0x00000000…000b

0x90c374…be45

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: 0x336ed437…cfc59c

3 conflicts on slot 0x3444391364…9ecbf3

← previous block·next block →recent activity