← previous blocknext block →recent activity

Analyzing

Block #86,611,550

20 transactions · 20 stateful · 2026-07-09 11:10:56 UTC

Parallelism

65/100

Blocked

45%

Avg conflicts / tx

1.25

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #86,611,550  ·  20 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

0x727fbce7…0c80

0x34b655…2a6f

14 touches
21 conflicts

0xcc3f7ee8…7924

0x34b655…2a6f

14 touches
21 conflicts

0x9966da31…0d0f

0x34b655…2a6f

14 touches
21 conflicts

0x922c7ebd…6600

0xc8689a…ee79

14 touches
21 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

14 touches
21 conflicts

0xfaef08b1…0696

0x34b655…2a6f

14 touches
21 conflicts

0xf7e59d30…11dd

0x34b655…2a6f

14 touches
21 conflicts

0x60c7217a…8c94

0x34b655…2a6f

14 touches
21 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 0x727fbce74b…da0c80

← previous block·next block →recent activity