← previous blocknext block →recent activity

Analyzing

Block #86,969,373

23 transactions · 22 stateful · 2026-07-11 03:03:03 UTC

Parallelism

70/100

Blocked

41%

Avg conflicts / tx

1.13

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #86,969,373  ·  23 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

0x0b202b66…0409

0x34b655…2a6f

12 touches
15 conflicts

0x922c7ebd…6600

0xc8689a…ee79

12 touches
15 conflicts

0xa1571d54…ae41

0x34b655…2a6f

12 touches
15 conflicts

0x511ecf07…8ed0

0x34b655…2a6f

12 touches
15 conflicts

0x727fbce7…0c80

0x34b655…2a6f

12 touches
15 conflicts

0x06aed19e…ca57

0x34b655…2a6f

12 touches
15 conflicts

0xc368d7fd…aaec

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

21 conflicts on slot 0xfaef08b108…f90696

← previous block·next block →recent activity