Block #73,490,469

← previous blocknext block →recent activity

Analyzing

Block #73,490,469

5 transactions · 4 stateful · 2026-05-09 16:08:00 UTC

Parallelism

60/100

Blocked

25%

Avg conflicts / tx

0.2

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,490,469  ·  5 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

0x22e295f5…1bef

0x065c9d…c394

4 touches
1 conflict

0x4d87512b…897c

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xa6fd78ef…c615

0x065c9d…c394

4 touches
1 conflict

0xae69c125…2379

0x2a68ba…90c5

2 touches
0 conflicts

0xc9e97522…3519

0x2a68ba…90c5

2 touches
0 conflicts

0x0175b7a6…1db9

0x6c4bfa…a540

2 touches
0 conflicts

0x0175b7a6…1dba

0x6c4bfa…a540

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 0x22e295f5d8…ac1bef

← previous block·next block →recent activity