← previous blocknext block →recent activity

Analyzing

Block #86,635,135

26 transactions · 20 stateful · 2026-07-09 13:48:26 UTC

Parallelism

65/100

Blocked

60%

Avg conflicts / tx

1.46

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #86,635,135  ·  26 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

0xa08f40b2…9a93

0x34b655…2a6f

14 touches
21 conflicts

0xfaef08b1…0696

0x34b655…2a6f

12 touches
15 conflicts

0x922c7ebd…6600

0xc8689a…ee79

6 touches
3 conflicts

0xd1ec0dfd…ccc0

0xc8689a…ee79

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x460a21c2…87f1

0x34b655…2a6f

6 touches
3 conflicts

0x5f72d58f…c445

0x34b655…2a6f

6 touches
3 conflicts

0xafe3acc8…5c1c

0x34b655…2a6f

6 touches
3 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 0xa08f40b255…099a93

← previous block·next block →recent activity