← previous blocknext block →recent activity

Analyzing

Block #86,613,414

29 transactions · 23 stateful · 2026-07-09 11:23:21 UTC

Parallelism

66/100

Blocked

57%

Avg conflicts / tx

1.69

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #86,613,414  ·  29 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0x64aaadbf…f9f3

0x34b655…2a6f

14 touches
21 conflicts

0xded7831c…3c4a

0x34b655…2a6f

12 touches
15 conflicts

0xd1ec0dfd…ccc0

0xc8689a…ee79

10 touches
10 conflicts

0x5bb46f6c…7693

0x34b655…2a6f

10 touches
10 conflicts

0x64a785e4…0110

0x34b655…2a6f

10 touches
10 conflicts

0x74fce6ad…7895

0x34b655…2a6f

10 touches
10 conflicts

0x890eac6e…1c0d

0x34b655…2a6f

10 touches
10 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