← previous blocknext block →recent activity

Analyzing

Block #86,804,021

24 transactions · 20 stateful · 2026-07-10 08:37:33 UTC

Parallelism

79/100

Blocked

45%

Avg conflicts / tx

0.71

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #86,804,021  ·  24 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

0xd8bc53a3…c2fe

0x34b655…2a6f

8 touches
6 conflicts

0xf06c427f…0a28

0xd32edf…ff58

7 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…001a

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…002a

0x1b6862…e19c

6 touches
3 conflicts

0xd59f6ed1…03e6

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x24e578ef…2049

0x34b655…2a6f

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 0xd8bc53a346…42c2fe

← previous block·next block →recent activity