← previous blocknext block →recent activity

Analyzing

Block #87,504,826

14 transactions · 13 stateful · 2026-07-13 14:43:13 UTC

Parallelism

79/100

Blocked

38%

Avg conflicts / tx

0.71

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #87,504,826  ·  14 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x10efb0c1…2ddc

0x34b655…2a6f

6 touches
3 conflicts

0xadd2210b…9e29

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x0733be30…112f

0x34b655…2a6f

6 touches
3 conflicts

0x0eeb2a30…6909

0x34b655…2a6f

6 touches
3 conflicts

0xf3d10975…0d07

0x34b655…2a6f

4 touches
1 conflict

0x3957d03b…147c

0x34b655…2a6f

4 touches
1 conflict

0x39a45f01…2b79

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 0x10efb0c15a…d22ddc

← previous block·next block →recent activity