← previous blocknext block →recent activity

Analyzing

Block #87,715,331

21 transactions · 15 stateful · 2026-07-14 14:11:45 UTC

Parallelism

71/100

Blocked

53%

Avg conflicts / tx

0.67

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #87,715,331  ·  21 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

6 touches
3 conflicts

0xc948dbdc…199a

0x34b655…2a6f

6 touches
3 conflicts

0x76c4d722…afa9

0x34b655…2a6f

6 touches
3 conflicts

0x03c2acba…6f0f

0x34b655…2a6f

4 touches
1 conflict

0x152f8e3d…3da0

0x34b655…2a6f

4 touches
1 conflict

0x38c6ff01…689f

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x4be9812b…48a9

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 0x6fe7d366be…a578ff

← previous block·next block →recent activity