Block #73,500,050

← previous blocknext block →recent activity

Analyzing

Block #73,500,050

23 transactions · 18 stateful · 2026-05-09 17:11:43 UTC

Parallelism

78/100

Blocked

39%

Avg conflicts / tx

0.57

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,500,050  ·  23 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

0xb81d3ee7…3947

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xb91a6f59…722c

0x34b655…2a6f

6 touches
3 conflicts

0x4d87512b…897c

0x065c9d…c394

6 touches
3 conflicts

0x8240d70c…7c3b

0x34b655…2a6f

6 touches
3 conflicts

0x070a562a…8147

0x34b655…2a6f

4 touches
1 conflict

0x0eac6378…36f4

0x34b655…2a6f

4 touches
1 conflict

0x1b159f3d…9163

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 0xb81d3ee780…143947

← previous block·next block →recent activity