← previous blocknext block →recent activity

Analyzing

Block #87,718,443

21 transactions · 21 stateful · 2026-07-14 14:32:41 UTC

Parallelism

81/100

Blocked

33%

Avg conflicts / tx

0.48

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #87,718,443  ·  21 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

0x0733be30…112f

0x34b655…2a6f

8 touches
6 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x3095aa84…e9e3

0x34b655…2a6f

6 touches
3 conflicts

0x4528594e…919a

0x34b655…2a6f

6 touches
3 conflicts

0x7c6cfc14…9958

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4ab

0x34b655…2a6f

4 touches
1 conflict

0x8031f204…99bc

0x34b655…2a6f

4 touches
1 conflict

0x8ed2e166…994b

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 0x0733be30d6…38112f

← previous block·next block →recent activity