← previous blocknext block →recent activity

Analyzing

Block #87,666,780

24 transactions · 19 stateful · 2026-07-14 08:46:51 UTC

Parallelism

83/100

Blocked

37%

Avg conflicts / tx

0.63

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #87,666,780  ·  24 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

0x7afbac8f…9cad

0x34b655…2a6f

6 touches
3 conflicts

0xc948dbdc…199a

0x34b655…2a6f

6 touches
3 conflicts

0xdb455dbf…e30c

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0x24f6d4ca…c33b

0x34b655…2a6f

6 touches
3 conflicts

0x1bc07c63…d6ad

0x34b655…2a6f

4 touches
1 conflict

0x389fdfc8…9f2e

0x34b655…2a6f

4 touches
1 conflict

0x45db1a5d…eab1

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 0x7afbac8f45…fb9cad

← previous block·next block →recent activity