← previous blocknext block →recent activity

Analyzing

Block #86,817,622

22 transactions · 22 stateful · 2026-07-10 10:08:27 UTC

Parallelism

77/100

Blocked

32%

Avg conflicts / tx

0.55

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #86,817,622  ·  22 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

0x7e5ea60a…c4aa

0x34b655…2a6f

8 touches
6 conflicts

0x92385428…6941

0x34b655…2a6f

8 touches
6 conflicts

0x0ee13be7…7b2c

0x34b655…2a6f

4 touches
1 conflict

0x14fe1598…d0ba

0x34b655…2a6f

4 touches
1 conflict

0x19ba76c3…6342

0x34b655…2a6f

4 touches
1 conflict

0x2550f1c1…a0e4

0x34b655…2a6f

4 touches
1 conflict

0x69ca0810…e942

0x34b655…2a6f

4 touches
1 conflict

0xfecb18c0…01ed

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

6 conflicts on slot 0x7e5ea60ab2…b0c4aa

← previous block·next block →recent activity