← previous blocknext block →recent activity

Analyzing

Block #73,532,605

7 transactions · 7 stateful · 2026-05-09 20:48:11 UTC

Parallelism

71/100

Blocked

14%

Avg conflicts / tx

0.29

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,532,605  ·  7 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

0xf6476f21…3580

0x34b655…2a6f

4 touches
1 conflict

0x693d979a…f2bd

0x34b655…2a6f

4 touches
1 conflict

0x6eba5e7f…4b52

0x34b655…2a6f

4 touches
1 conflict

0x2dd17449…6a54

0x34b655…2a6f

2 touches
0 conflicts

0x8240d70c…7c3b

0x34b655…2a6f

2 touches
0 conflicts

0x8db1e0f2…2fcf

0x34b655…2a6f

2 touches
0 conflicts

0xac8e97a0…8426

0x34b655…2a6f

2 touches
0 conflicts

0xb3b6dc1b…1293

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 0xf6476f21e7…f83580

← previous block·next block →recent activity