Block #73,697,412

← previous blocknext block →recent activity

Analyzing

Block #73,697,412

10 transactions · 8 stateful · 2026-05-10 15:10:59 UTC

Parallelism

80/100

Blocked

13%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,697,412  ·  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

0x529acb6a…fcc6

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xd05f6863…7596

0x065c9d…c394

3 touches
1 conflict

0x4556d88c…82cf

0x065c9d…c394

3 touches
1 conflict

0x0ac31945…2c72

0x065c9d…c394

2 touches
0 conflicts

0x51b05589…27b7

0x065c9d…c394

2 touches
0 conflicts

0xae69c125…2379

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 0x529acb6ad1…f0fcc6

← previous block·next block →recent activity