← previous blocknext block →recent activity

Analyzing

Block #87,134,930

18 transactions · 16 stateful · 2026-07-11 21:28:54 UTC

Parallelism

83/100

Blocked

38%

Avg conflicts / tx

0.44

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #87,134,930  ·  18 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x56b5f5c0…a3ad

0x34b655…2a6f

6 touches
3 conflicts

0xef65bff3…7c9d

0x2a68ba…90c5

4 touches
1 conflict

0x1321736a…43e3

0x34b655…2a6f

4 touches
1 conflict

0x1a3d2527…8ca0

0x34b655…2a6f

4 touches
1 conflict

0x21082490…de66

0x34b655…2a6f

4 touches
1 conflict

0x2533f477…a43b

0x34b655…2a6f

4 touches
1 conflict

0x26cdc92a…04ba

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

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

3 conflicts on slot 0x56b5f5c03e…07a3ad

← previous block·next block →recent activity