← previous blocknext block →recent activity

Analyzing

Block #87,063,636

22 transactions · 21 stateful · 2026-07-11 13:32:47 UTC

Parallelism

68/100

Blocked

38%

Avg conflicts / tx

0.77

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #87,063,636  ·  22 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

10 touches
10 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

8 touches
6 conflicts

0x5d863b2f…bd28

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x56b5f5c0…a3ad

0x34b655…2a6f

6 touches
3 conflicts

0x91359e02…8894

0x34b655…2a6f

4 touches
1 conflict

0xad1241a7…17f3

0x34b655…2a6f

4 touches
1 conflict

0xbf47a88f…7b7e

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

← previous block·next block →recent activity