Block #73,348,830

← previous blocknext block →recent activity

Analyzing

Block #73,348,830

15 transactions · 13 stateful · 2026-05-09 00:25:27 UTC

Parallelism

87/100

Blocked

31%

Avg conflicts / tx

0.33

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,348,830  ·  15 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

0x318ac0bb…6b9c

0x34b655…2a6f

4 touches
1 conflict

0x4b268018…02fb

0x34b655…2a6f

4 touches
1 conflict

0x60f7fbaf…bd58

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0xac808a27…82db

0x34b655…2a6f

4 touches
1 conflict

0xd0f6f4f2…dffa

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x8a35acfb…d1ae

0x8d66a4…3095

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

1 conflict on slot 0x318ac0bba0…ce6b9c

← previous block·next block →recent activity