Block #73,029,641

← previous blocknext block →recent activity

Analyzing

Block #73,029,641

10 transactions · 9 stateful · 2026-05-07 13:01:47 UTC

Parallelism

80/100

Blocked

11%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,029,641  ·  10 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

0xfbbc35e2…f66b

0x34b655…2a6f

4 touches
1 conflict

0x5d70606a…1d53

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x0b390c61…dc07

0x065c9d…c394

2 touches
0 conflicts

0x1c234d14…c743

0x065c9d…c394

2 touches
0 conflicts

0x230de0e9…b0f4

0x065c9d…c394

2 touches
0 conflicts

0x250027b2…1f52

0x065c9d…c394

2 touches
0 conflicts

0xbd7e37a9…9eb5

0x065c9d…c394

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 0xfbbc35e2ac…4ff66b

← previous block·next block →recent activity