Block #73,679,372

← previous blocknext block →recent activity

Analyzing

Block #73,679,372

29 transactions · 23 stateful · 2026-05-10 13:09:25 UTC

Parallelism

69/100

Blocked

48%

Avg conflicts / tx

1.38

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #73,679,372  ·  29 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

18 touches
36 conflicts

0x6e785a76…8a02

0x34b655…2a6f

6 touches
3 conflicts

0x3e733ae4…4598

0x34b655…2a6f

6 touches
3 conflicts

0xff57e100…9d50

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0x85a88798…f85e

0x34b655…2a6f

4 touches
1 conflict

0x8aa1941d…2988

0x34b655…2a6f

4 touches
1 conflict

0xb08dfc05…4923

0x34b655…2a6f

4 touches
1 conflict

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

36 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity