← previous blocknext block →recent activity

Analyzing

Block #85,139,264

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

Parallelism

64/100

Blocked

50%

Avg conflicts / tx

0.95

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #85,139,264  ·  22 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x7c63ea28…e8af

0x34b655…2a6f

12 touches
15 conflicts

0xaa99c369…263d

0x34b655…2a6f

10 touches
10 conflicts

0x4fefe22e…64d4

0x34b655…2a6f

8 touches
6 conflicts

0x7066502a…11f7

0x34b655…2a6f

8 touches
6 conflicts

0x7c0bdc54…9dde

0x34b655…2a6f

8 touches
6 conflicts

0x922c7ebd…6600

0xc8689a…ee79

8 touches
6 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

8 touches
6 conflicts

0xaa48195d…ffee

0x34b655…2a6f

8 touches
6 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

15 conflicts on slot 0x7c63ea28d6…76e8af

← previous block·next block →recent activity