Block #73,578,656

← previous blocknext block →recent activity

Analyzing

Block #73,578,656

12 transactions · 10 stateful · 2026-05-10 01:54:01 UTC

Parallelism

83/100

Blocked

10%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,578,656  ·  12 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

0x4d87512b…897c

0x065c9d…c394

4 touches
1 conflict

0xf2e85cfb…91b5

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xa04e07f1…8e6e

0x065c9d…c394

3 touches
1 conflict

0xaaff8140…a85d

0x065c9d…c394

2 touches
0 conflicts

0xc6147686…98fc

0x065c9d…c394

2 touches
0 conflicts

0xd8307c7c…1944

0x065c9d…c394

2 touches
0 conflicts

0xf8fbc8fa…6a07

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

1 conflict on slot 0x4d87512b00…43897c

← previous block·next block →recent activity