Block #73,506,839

← previous blocknext block →recent activity

Analyzing

Block #73,506,839

10 transactions · 7 stateful · 2026-05-09 17:57:02 UTC

Parallelism

70/100

Blocked

43%

Avg conflicts / tx

0.4

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,506,839  ·  10 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

0x4d87512b…897c

0x065c9d…c394

4 touches
1 conflict

0x31202e80…6341

0x065c9d…c394

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x22e295f5…1bef

0x065c9d…c394

4 touches
1 conflict

0x48cdb415…b5c5

0x065c9d…c394

3 touches
1 conflict

0x115666ed…d560

0x065c9d…c394

3 touches
1 conflict

0x4018bf8d…2217

0x065c9d…c394

3 touches
1 conflict

0xd615f935…2ca2

0x065c9d…c394

3 touches
1 conflict

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