Block #73,506,880

← previous blocknext block →recent activity

Analyzing

Block #73,506,880

24 transactions · 17 stateful · 2026-05-09 17:57:19 UTC

Parallelism

79/100

Blocked

41%

Avg conflicts / tx

0.58

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,506,880  ·  24 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x3a429191…9cda

0x34b655…2a6f

8 touches
6 conflicts

0x8d20a051…0d5f

0x34b655…2a6f

6 touches
3 conflicts

0xa9988419…9f45

0x34b655…2a6f

6 touches
3 conflicts

0x60f7fbaf…bd58

0x34b655…2a6f

6 touches
3 conflicts

0x8a35acfb…d1ad

0x8d66a4…3095

6 touches
3 conflicts

0x374426df…f445

0xc8689a…ee79

6 touches
3 conflicts

0xb709a0ae…2f7a

0xd32edf…ff58

5 touches
3 conflicts

0x23b2399c…6e4b

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: 0x34b6552d…112a6f

6 conflicts on slot 0x3a42919159…6b9cda

← previous block·next block →recent activity