Block #73,594,345

← previous blocknext block →recent activity

Analyzing

Block #73,594,345

19 transactions · 14 stateful · 2026-05-10 03:38:20 UTC

Parallelism

79/100

Blocked

50%

Avg conflicts / tx

0.58

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,594,345  ·  19 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x2bf6eec9…5f52

0xd32edf…ff58

7 touches
6 conflicts

0x2905340c…dbc6

0x34b655…2a6f

4 touches
1 conflict

0xc6615a36…3cf0

0x34b655…2a6f

4 touches
1 conflict

0x4d87512b…897c

0x065c9d…c394

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x17606ba6…1b6e

0x754704…b603

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

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: 0xd32edf66…9fff58

6 conflicts on slot 0x2bf6eec98e…385f52

← previous block·next block →recent activity