Block #73,970,904

← previous blocknext block →recent activity

Analyzing

Block #73,970,904

14 transactions · 13 stateful · 2026-05-11 21:41:37 UTC

Parallelism

71/100

Blocked

23%

Avg conflicts / tx

0.43

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,970,904  ·  14 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x7cee1be1…e770

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x9ea57326…329f

0x34b655…2a6f

8 touches
6 conflicts

0xfa2527aa…9dd5

0x34b655…2a6f

6 touches
3 conflicts

0x2877f440…c2c8

0x34b655…2a6f

6 touches
3 conflicts

0x53b8bf67…b6d4

0x34b655…2a6f

6 touches
3 conflicts

0x85a88798…f85e

0x34b655…2a6f

6 touches
3 conflicts

0xa15427f6…d932

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

6 conflicts on slot 0x7cee1be1f4…b4e770

← previous block·next block →recent activity