Block #73,176,462

← previous blocknext block →recent activity

Analyzing

Block #73,176,462

9 transactions · 9 stateful · 2026-05-08 05:18:33 UTC

Parallelism

67/100

Blocked

22%

Avg conflicts / tx

0.56

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,176,462  ·  9 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xf2f76ab3…623e

0x2a68ba…90c5

6 touches
3 conflicts

0x8e66da19…66b6

0x065c9d…c394

4 touches
1 conflict

0xff23668e…e618

0x065c9d…c394

4 touches
1 conflict

0x7308a1b8…1809

0x065c9d…c394

3 touches
1 conflict

0xbfed7bee…5018

0x065c9d…c394

3 touches
1 conflict

0xfc01c3cd…3055

0x065c9d…c394

3 touches
1 conflict

0x95adc56e…b604

0x34b655…2a6f

2 touches
0 conflicts

0xd984a5e4…5cfc

0x34b655…2a6f

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: 0x2a68ba18…8e90c5

3 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity