← previous blocknext block →recent activity

Analyzing

Block #73,648,721

27 transactions · 23 stateful · 2026-05-10 09:42:34 UTC

Parallelism

63/100

Blocked

43%

Avg conflicts / tx

1.44

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #73,648,721  ·  27 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

0xa91c899f…6ee3

0x34b655…2a6f

16 touches
28 conflicts

0x462d8e25…1e49

0x34b655…2a6f

14 touches
21 conflicts

0xedb848fe…6534

0x34b655…2a6f

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xd49762c9…1359

0x34b655…2a6f

8 touches
6 conflicts

0xc6417de0…2191

0xc8689a…ee79

8 touches
6 conflicts

0x15d039e7…4bb6

0x34b655…2a6f

8 touches
6 conflicts

0x0520da1d…c88e

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

28 conflicts on slot 0xa91c899f02…fa6ee3

← previous block·next block →recent activity