← previous blocknext block →recent activity

Analyzing

Block #87,715,847

24 transactions · 21 stateful · 2026-07-14 14:15:14 UTC

Parallelism

75/100

Blocked

43%

Avg conflicts / tx

0.88

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #87,715,847  ·  24 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

0x6fe7d366…78ff

0x34b655…2a6f

12 touches
15 conflicts

0x0ba865dd…a249

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x2de3014c…0346

0x34b655…2a6f

6 touches
3 conflicts

0x74fd0a9b…3aaa

0x34b655…2a6f

6 touches
3 conflicts

0x5c3cb0f1…a9fa

0x34b655…2a6f

6 touches
3 conflicts

0xbf78ee7f…e7fd

0x34b655…2a6f

6 touches
3 conflicts

0x5170a218…3a84

0xc8689a…ee79

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

15 conflicts on slot 0x6fe7d366be…a578ff

← previous block·next block →recent activity