← previous blocknext block →recent activity

Analyzing

Block #86,808,020

19 transactions · 19 stateful · 2026-07-10 09:04:15 UTC

Parallelism

63/100

Blocked

53%

Avg conflicts / tx

1.53

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #86,808,020  ·  19 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xfaef08b1…0696

0x34b655…2a6f

14 touches
21 conflicts

0xd3ef5630…0de9

0x34b655…2a6f

14 touches
21 conflicts

0x7506443a…4820

0x34b655…2a6f

14 touches
21 conflicts

0x3483ab79…8ed3

0x34b655…2a6f

12 touches
15 conflicts

0x922c7ebd…6600

0xc8689a…ee79

12 touches
15 conflicts

0x1bfc029c…f91e

0x34b655…2a6f

12 touches
15 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

12 touches
15 conflicts

0x63c900f4…2600

0x34b655…2a6f

12 touches
15 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

21 conflicts on slot 0xfaef08b108…f90696

← previous block·next block →recent activity