← previous blocknext block →recent activity

Analyzing

Block #86,772,036

21 transactions · 17 stateful · 2026-07-10 05:04:03 UTC

Parallelism

81/100

Blocked

47%

Avg conflicts / tx

0.67

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,772,036  ·  21 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

8 touches
6 conflicts

0x92385428…6941

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…000a

0x90c374…be45

8 touches
6 conflicts

0x00000000…000b

0x90c374…be45

8 touches
6 conflicts

0x085c9fac…8fcf

0x8d1565…6723

6 touches
3 conflicts

0x5f72d58f…c445

0x34b655…2a6f

6 touches
3 conflicts

0x93c58e4d…9b32

0x336ed4…c59c

6 touches
3 conflicts

0x10a2bd5d…ad6d

0x8d1565…6723

6 touches
3 conflicts

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

6 conflicts on slot 0x7e5ea60ab2…b0c4aa

← previous block·next block →recent activity