← previous blocknext block →recent activity

Analyzing

Block #85,177,471

22 transactions · 18 stateful · 2026-07-02 19:44:25 UTC

Parallelism

45/100

Blocked

67%

Avg conflicts / tx

2.95

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #85,177,471  ·  22 txs across 12 waves  ·  depth 12
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

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

0x22e0cc1d…ad0d

0x34b655…2a6f

18 touches
36 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

16 touches
28 conflicts

0xfc366eef…6209

0x34b655…2a6f

14 touches
21 conflicts

0x326a02b5…8dad

0x34b655…2a6f

12 touches
15 conflicts

0x6fbc2e5a…e69c

0x34b655…2a6f

10 touches
10 conflicts

0x922c7ebd…6600

0xc8689a…ee79

8 touches
6 conflicts

0x006c3b86…59a9

0x34b655…2a6f

8 touches
6 conflicts

0x51a914cf…a822

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

36 conflicts on slot 0x22e0cc1d4a…90ad0d

← previous block·next block →recent activity