← previous blocknext block →recent activity

Analyzing

Block #87,347,609

17 transactions · 16 stateful · 2026-07-12 21:11:45 UTC

Parallelism

76/100

Blocked

50%

Avg conflicts / tx

0.82

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #87,347,609  ·  17 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

0x94ba9c4a…41d8

0x34b655…2a6f

8 touches
6 conflicts

0x6278b1b2…ba7b

0x34b655…2a6f

6 touches
3 conflicts

0x0733be30…112f

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4ab

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x92385428…6941

0x34b655…2a6f

6 touches
3 conflicts

0x6f95cc9f…e9b5

0x34b655…2a6f

4 touches
1 conflict

0x85a88798…f85e

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

6 conflicts on slot 0x94ba9c4a07…0c41d8

← previous block·next block →recent activity