← previous blocknext block →recent activity

Analyzing

Block #87,066,204

30 transactions · 19 stateful · 2026-07-11 13:49:54 UTC

Parallelism

90/100

Blocked

32%

Avg conflicts / tx

0.27

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #87,066,204  ·  30 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0xc36fa358…24cb

0x34b655…2a6f

6 touches
3 conflicts

0x14ed37a5…2bf0

0xd32edf…ff58

5 touches
3 conflicts

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0x8267cc91…78bc

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xd08d1657…e444

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 0x7e5ea60ab2…b0c4aa

← previous block·next block →recent activity