Block #73,308,189

← previous blocknext block →recent activity

Analyzing

Block #73,308,189

13 transactions · 8 stateful · 2026-05-08 19:55:03 UTC

Parallelism

85/100

Blocked

13%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,308,189  ·  13 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

0x516fb794…f4ee

0x34b655…2a6f

4 touches
1 conflict

0x6fa48833…eb0d

0x34b655…2a6f

4 touches
1 conflict

0xb389d45f…8a4c

0x34b655…2a6f

4 touches
1 conflict

0xfa2527aa…9dd5

0x34b655…2a6f

4 touches
1 conflict

0x0b390c61…dc07

0x065c9d…c394

2 touches
0 conflicts

0x32786b8e…319c

0x065c9d…c394

2 touches
0 conflicts

0xa22fbb31…8fb3

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 0x516fb794e5…9af4ee

← previous block·next block →recent activity