← previous blocknext block →recent activity

Analyzing

Block #86,628,393

31 transactions · 26 stateful · 2026-07-09 13:03:21 UTC

Parallelism

71/100

Blocked

38%

Avg conflicts / tx

1.19

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #86,628,393  ·  31 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

0xfaef08b1…0696

0x34b655…2a6f

16 touches
28 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

10 touches
10 conflicts

0x87ee379a…cd9e

0x34b655…2a6f

10 touches
10 conflicts

0xb0bc3bf8…e2b1

0x34b655…2a6f

10 touches
10 conflicts

0x38d19a60…c141

0x34b655…2a6f

8 touches
6 conflicts

0x3c12ef6b…070a

0x34b655…2a6f

8 touches
6 conflicts

0x3d4584df…ffed

0x34b655…2a6f

8 touches
6 conflicts

0x85eb1316…bb9e

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

28 conflicts on slot 0xfaef08b108…f90696

← previous block·next block →recent activity