← previous blocknext block →recent activity

Analyzing

Block #73,653,555

36 transactions · 26 stateful · 2026-05-10 10:15:08 UTC

Parallelism

78/100

Blocked

46%

Avg conflicts / tx

1.06

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #73,653,555  ·  36 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

0xf2438038…5fa7

0x34b655…2a6f

14 touches
21 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x4582e32d…1abe

0x34b655…2a6f

8 touches
6 conflicts

0x5f450515…3bc4

0x34b655…2a6f

8 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

8 touches
6 conflicts

0x85a88798…f85e

0x34b655…2a6f

8 touches
6 conflicts

0x8aa1941d…2988

0x34b655…2a6f

8 touches
6 conflicts

0x97d5efed…1aa4

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

21 conflicts on slot 0xf2438038b6…475fa7

← previous block·next block →recent activity