← previous blocknext block →recent activity

Analyzing

Block #87,735,889

22 transactions · 19 stateful · 2026-07-14 16:29:22 UTC

Parallelism

73/100

Blocked

42%

Avg conflicts / tx

0.91

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #87,735,889  ·  22 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

0xe3ce81c6…d48d

0x34b655…2a6f

10 touches
10 conflicts

0x0733be30…112f

0x34b655…2a6f

8 touches
6 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

8 touches
6 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x49ec39d3…0b07

0x34b655…2a6f

4 touches
1 conflict

0x49ec39d3…0b08

0x34b655…2a6f

4 touches
1 conflict

0x5c3cb0f1…a9fa

0x34b655…2a6f

4 touches
1 conflict

0x5c591136…d322

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

10 conflicts on slot 0xe3ce81c686…e3d48d

← previous block·next block →recent activity