Block #73,503,184

← previous blocknext block →recent activity

Analyzing

Block #73,503,184

16 transactions · 12 stateful · 2026-05-09 17:32:38 UTC

Parallelism

88/100

Blocked

8%

Avg conflicts / tx

0.06

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,503,184  ·  16 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

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xa9287840…1e02

0x065c9d…c394

4 touches
1 conflict

0x22e295f5…1bef

0x065c9d…c394

4 touches
1 conflict

0x2909633f…08a4

0x065c9d…c394

3 touches
1 conflict

0x0f637fa5…56e2

0x065c9d…c394

3 touches
1 conflict

0xed77ece2…d0f5

0x065c9d…c394

2 touches
0 conflicts

0xf80a13fb…0763

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