← previous blocknext block →recent activity

Analyzing

Block #86,704,119

19 transactions · 18 stateful · 2026-07-09 21:30:14 UTC

Parallelism

58/100

Blocked

50%

Avg conflicts / tx

1.37

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #86,704,119  ·  19 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

0x63c900f4…2600

0x34b655…2a6f

12 touches
15 conflicts

0x22bc4ea4…5c8a

0x34b655…2a6f

10 touches
10 conflicts

0x2d7ea048…d78e

0x34b655…2a6f

10 touches
10 conflicts

0x922c7ebd…6600

0xc8689a…ee79

10 touches
10 conflicts

0xa3e06ffb…6c2b

0x34b655…2a6f

10 touches
10 conflicts

0xbfdd8306…fa07

0x34b655…2a6f

10 touches
10 conflicts

0xe57232b3…0fbf

0x34b655…2a6f

10 touches
10 conflicts

0xf37957e9…3cc9

0x34b655…2a6f

10 touches
10 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 0x63c900f479…962600

← previous block·next block →recent activity