← previous blocknext block →recent activity

Analyzing

Block #86,663,711

26 transactions · 20 stateful · 2026-07-09 17:00:35 UTC

Parallelism

65/100

Blocked

50%

Avg conflicts / tx

1

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #86,663,711  ·  26 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0xd99b3b64…1c95

0x34b655…2a6f

10 touches
10 conflicts

0x12573732…e891

0x34b655…2a6f

8 touches
6 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

8 touches
6 conflicts

0x2d7ea048…d78e

0x34b655…2a6f

8 touches
6 conflicts

0x3d4584df…ffed

0x34b655…2a6f

8 touches
6 conflicts

0x4458db0c…b00f

0x34b655…2a6f

8 touches
6 conflicts

0x60c7217a…8c94

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

10 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity