Block #73,677,712

← previous blocknext block →recent activity

Analyzing

Block #73,677,712

8 transactions · 6 stateful · 2026-05-10 12:58:12 UTC

Parallelism

63/100

Blocked

33%

Avg conflicts / tx

0.25

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,677,712  ·  8 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

0x596198ad…216c

0x065c9d…c394

4 touches
1 conflict

0x0ac31945…2c72

0x065c9d…c394

4 touches
1 conflict

0x71a24d67…041f

0x065c9d…c394

3 touches
1 conflict

0x16d143eb…21b2

0x065c9d…c394

3 touches
1 conflict

0x1ef8c367…6599

0x065c9d…c394

3 touches
1 conflict

0xba5743c7…21c3

0x1b6862…e19c

2 touches
0 conflicts

0x046a928e…0012

0x2a68ba…90c5

2 touches
0 conflicts

0xc9e97522…3519

0x2a68ba…90c5

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: 0x065c9d28…a9c394

1 conflict on slot 0x596198adb9…59216c

← previous block·next block →recent activity