Block #73,201,673

← previous blocknext block →recent activity

Analyzing

Block #73,201,673

25 transactions · 23 stateful · 2026-05-08 08:06:31 UTC

Parallelism

72/100

Blocked

48%

Avg conflicts / tx

1.16

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,201,673  ·  25 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

14 touches
21 conflicts

0x3b8ffd61…f3ad

0x34b655…2a6f

8 touches
6 conflicts

0x28c180e1…f1e2

0x34b655…2a6f

8 touches
6 conflicts

0x79bf6be7…ddf4

0x34b655…2a6f

8 touches
6 conflicts

0xef17b8cd…9511

0x34b655…2a6f

8 touches
6 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x904fc3c0…00ec

0x34b655…2a6f

6 touches
3 conflicts

0xa92c8763…6d7f

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

21 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity