Block #73,482,670

← previous blocknext block →recent activity

Analyzing

Block #73,482,670

12 transactions · 11 stateful · 2026-05-09 15:15:59 UTC

Parallelism

83/100

Blocked

18%

Avg conflicts / tx

0.17

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,482,670  ·  12 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x206f4379…e08a

0x34b655…2a6f

4 touches
1 conflict

0xfac43f12…b842

0x34b655…2a6f

4 touches
1 conflict

0x6713b018…05f3

0x34b655…2a6f

4 touches
1 conflict

0x0b28bf77…e53a

0x34b655…2a6f

4 touches
1 conflict

0x57de3828…3fbb

0x34b655…2a6f

2 touches
0 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

2 touches
0 conflicts

0x6eba5e7f…4b52

0x34b655…2a6f

2 touches
0 conflicts

0x908d4442…2c4b

0x34b655…2a6f

2 touches
0 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

1 conflict on slot 0x206f43799d…55e08a

← previous block·next block →recent activity