Block #73,033,974

← previous blocknext block →recent activity

Analyzing

Block #73,033,974

25 transactions · 19 stateful · 2026-05-07 13:30:39 UTC

Parallelism

76/100

Blocked

53%

Avg conflicts / tx

1.2

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,033,974  ·  25 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x0a2250a8…3cb1

0x34b655…2a6f

10 touches
10 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

10 touches
10 conflicts

0x7b97d40a…09ed

0x34b655…2a6f

10 touches
10 conflicts

0x908d4442…2c4b

0x34b655…2a6f

10 touches
10 conflicts

0x00000000…0002

0xd574ca…7ab1

10 touches
10 conflicts

0xaa3492db…3703

0x34b655…2a6f

8 touches
6 conflicts

0x8db1e0f2…2fcf

0x34b655…2a6f

8 touches
6 conflicts

0xf853eb8e…4027

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

10 conflicts on slot 0x0a2250a863…a83cb1

← previous block·next block →recent activity