← previous blocknext block →recent activity

Analyzing

Block #85,126,119

29 transactions · 26 stateful · 2026-07-02 14:02:13 UTC

Parallelism

62/100

Blocked

54%

Avg conflicts / tx

1.17

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #85,126,119  ·  29 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0x03fb27fd…0c06

0x34b655…2a6f

8 touches
6 conflicts

0x922c7ebd…6600

0xc8689a…ee79

8 touches
6 conflicts

0x8e5cc690…b06b

0x34b655…2a6f

8 touches
6 conflicts

0x9f40a209…1193

0x34b655…2a6f

8 touches
6 conflicts

0xa6ddb1ef…ac64

0x34b655…2a6f

8 touches
6 conflicts

0xb4e00a70…4c3e

0x34b655…2a6f

8 touches
6 conflicts

0xc3389789…adbf

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