← previous blocknext block →recent activity

Analyzing

Block #86,221,171

22 transactions · 18 stateful · 2026-07-07 15:41:02 UTC

Parallelism

77/100

Blocked

39%

Avg conflicts / tx

0.68

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #86,221,171  ·  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

0x96dd83e6…a507

0x34b655…2a6f

10 touches
10 conflicts

0x9651272d…cddd

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…0002

0x04fdea…47d7

6 touches
3 conflicts

0x5eace3d2…4bec

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…002f

0x1b6862…e19c

4 touches
1 conflict

0x45b67460…28ac

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

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 0x96dd83e650…3fa507

← previous block·next block →recent activity