← previous blocknext block →recent activity

Analyzing

Block #87,698,108

19 transactions · 18 stateful · 2026-07-14 12:16:13 UTC

Parallelism

68/100

Blocked

50%

Avg conflicts / tx

1

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #87,698,108  ·  19 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

0x8eedf936…a0c3

0x34b655…2a6f

8 touches
6 conflicts

0x6fe7d366…78ff

0x34b655…2a6f

8 touches
6 conflicts

0xee0cc1b7…de22

0x34b655…2a6f

8 touches
6 conflicts

0x1f81b064…5fc2

0x34b655…2a6f

6 touches
3 conflicts

0x4c188934…158e

0x34b655…2a6f

6 touches
3 conflicts

0x536588d3…19c5

0x34b655…2a6f

6 touches
3 conflicts

0x1716b13d…99cc

0xc8689a…ee79

6 touches
3 conflicts

0x0733be30…112f

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

6 conflicts on slot 0x8eedf9362f…60a0c3

← previous block·next block →recent activity