← previous blocknext block →recent activity

Analyzing

Block #73,647,627

35 transactions · 23 stateful · 2026-05-10 09:35:11 UTC

Parallelism

77/100

Blocked

61%

Avg conflicts / tx

1.2

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #73,647,627  ·  35 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xd98b3c10…67b8

0x34b655…2a6f

14 touches
21 conflicts

0x1c1ecaf9…4e00

0xd32edf…ff58

11 touches
15 conflicts

0x8a2657f5…e008

0x34b655…2a6f

8 touches
6 conflicts

0xa91c899f…6ee3

0x34b655…2a6f

8 touches
6 conflicts

0xa486f342…64d5

0x34b655…2a6f

6 touches
3 conflicts

0x408e66bb…3d6b

0x34b655…2a6f

6 touches
3 conflicts

0xab41bf9c…66a9

0x34b655…2a6f

6 touches
3 conflicts

0x28c180e1…f1e2

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: 0x34b6552d…112a6f

21 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity