← previous blocknext block →recent activity

Analyzing

Block #86,708,988

22 transactions · 20 stateful · 2026-07-09 22:02:43 UTC

Parallelism

59/100

Blocked

50%

Avg conflicts / tx

1.27

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #86,708,988  ·  22 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

12 touches
15 conflicts

0x64a785e4…0110

0x34b655…2a6f

10 touches
10 conflicts

0xa5ab7b8a…c97b

0x34b655…2a6f

8 touches
6 conflicts

0xafe3acc8…5c1c

0x34b655…2a6f

8 touches
6 conflicts

0xfaef08b1…0696

0x34b655…2a6f

8 touches
6 conflicts

0xfec3435f…4a72

0x34b655…2a6f

8 touches
6 conflicts

0xd1ec0dfd…ccc0

0xc8689a…ee79

8 touches
6 conflicts

0x546671c8…080a

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

15 conflicts on slot 0xa08f40b255…099a93

← previous block·next block →recent activity