Block #73,744,529

← previous blocknext block →recent activity

Analyzing

Block #73,744,529

30 transactions · 25 stateful · 2026-05-10 20:28:58 UTC

Parallelism

67/100

Blocked

68%

Avg conflicts / tx

2.13

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #73,744,529  ·  30 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

0x00000000…0002

0xab3526…fa38

20 touches
45 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

12 touches
15 conflicts

0x00000000…002d

0x1b6862…e19c

6 touches
3 conflicts

0xc6417de0…2191

0xc8689a…ee79

6 touches
3 conflicts

0x00000000…001d

0x1b6862…e19c

6 touches
3 conflicts

0x7b97d40a…09ed

0x34b655…2a6f

6 touches
3 conflicts

0x45b9e08c…a11b

0x34b655…2a6f

6 touches
3 conflicts

0x26bb6db7…f861

0x1b6862…e19c

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: 0xab35264b…1cfa38

45 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity