← previous blocknext block →recent activity

Analyzing

Block #87,661,429

21 transactions · 17 stateful · 2026-07-14 08:11:05 UTC

Parallelism

76/100

Blocked

41%

Avg conflicts / tx

0.67

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #87,661,429  ·  21 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x59dccbd8…2bf6

0x34b655…2a6f

10 touches
10 conflicts

0xc948dbdc…199a

0x34b655…2a6f

6 touches
3 conflicts

0xd35bb5ac…3586

0x065c9d…c394

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…00c9

0x34b655…2a6f

4 touches
1 conflict

0x1f2f3106…6b83

0x34b655…2a6f

4 touches
1 conflict

0x28504822…ded6

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 0x59dccbd857…c52bf6

← previous block·next block →recent activity