Block #73,359,469

← previous blocknext block →recent activity

Analyzing

Block #73,359,469

12 transactions · 11 stateful · 2026-05-09 01:36:10 UTC

Parallelism

50/100

Blocked

45%

Avg conflicts / tx

1

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,359,469  ·  12 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

0x42446806…33dd

0x34b655…2a6f

8 touches
6 conflicts

0x1fcacf75…7ade

0x34b655…2a6f

6 touches
3 conflicts

0x8db1e0f2…2fcf

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x908d4442…2c4b

0x34b655…2a6f

6 touches
3 conflicts

0xf853eb8e…4027

0x34b655…2a6f

6 touches
3 conflicts

0xfac43f12…b842

0x34b655…2a6f

6 touches
3 conflicts

0x1b9e654e…0a08

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 0x4244680631…fd33dd

← previous block·next block →recent activity