← previous blocknext block →recent activity

Analyzing

Block #87,419,797

18 transactions · 17 stateful · 2026-07-13 05:14:36 UTC

Parallelism

78/100

Blocked

47%

Avg conflicts / tx

0.72

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #87,419,797  ·  18 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

0x2b5101ac…090b

0x34b655…2a6f

8 touches
6 conflicts

0x11c40774…adbe

0x34b655…2a6f

8 touches
6 conflicts

0x0a8f8b9c…3046

0x34b655…2a6f

6 touches
3 conflicts

0x1baca9c3…2b23

0x34b655…2a6f

6 touches
3 conflicts

0x9e9ffe69…e039

0x34b655…2a6f

6 touches
3 conflicts

0xc1a4c088…e828

0x34b655…2a6f

6 touches
3 conflicts

0x59a54ff4…d21b

0x34b655…2a6f

6 touches
3 conflicts

0xe181f491…f4e3

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 0x2b5101acd1…7c090b

← previous block·next block →recent activity