Block #73,446,523

← previous blocknext block →recent activity

Analyzing

Block #73,446,523

10 transactions · 7 stateful · 2026-05-09 11:15:30 UTC

Parallelism

70/100

Blocked

29%

Avg conflicts / tx

0.3

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,446,523  ·  10 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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…003d

0x065c9d…c394

6 touches
3 conflicts

0x22e295f5…1bef

0x065c9d…c394

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x2877f440…c2c8

0x34b655…2a6f

2 touches
0 conflicts

0x312c5cb2…7f25

0x34b655…2a6f

2 touches
0 conflicts

0x8240d70c…7c3b

0x34b655…2a6f

2 touches
0 conflicts

0xab910e7d…556a

0x34b655…2a6f

2 touches
0 conflicts

0xcc8f294b…ddcb

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: 0x065c9d28…a9c394

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity