Block #73,482,667

← previous blocknext block →recent activity

Analyzing

Block #73,482,667

11 transactions · 9 stateful · 2026-05-09 15:15:58 UTC

Parallelism

82/100

Blocked

22%

Avg conflicts / tx

0.18

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,482,667  ·  11 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x1fcacf75…7ade

0x34b655…2a6f

4 touches
1 conflict

0xa91c899f…6ee3

0x34b655…2a6f

4 touches
1 conflict

0x8a35acfb…d1ac

0x8d66a4…3095

4 touches
1 conflict

0x96504a63…52d2

0x8d66a4…3095

4 touches
1 conflict

0x2f75f51f…9376

0x065c9d…c394

2 touches
0 conflicts

0x426032f2…c364

0x065c9d…c394

2 touches
0 conflicts

0x7234c38a…e685

0x065c9d…c394

2 touches
0 conflicts

0x1b9e654e…0a08

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

1 conflict on slot 0x1fcacf75ae…f77ade

← previous block·next block →recent activity