Block #73,533,484

← previous blocknext block →recent activity

Analyzing

Block #73,533,484

14 transactions · 10 stateful · 2026-05-09 20:54:02 UTC

Parallelism

64/100

Blocked

40%

Avg conflicts / tx

0.64

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,533,484  ·  14 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x046a928e…0012

0x2a68ba…90c5

8 touches
6 conflicts

0x22e295f5…1bef

0x065c9d…c394

6 touches
3 conflicts

0x4697eb3b…c257

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x9784b4ec…7665

0x065c9d…c394

3 touches
1 conflict

0x096d5b18…f7a3

0x065c9d…c394

3 touches
1 conflict

0x8c6960b5…31d5

0x065c9d…c394

2 touches
0 conflicts

0xfa0fae88…4a85

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: 0x2a68ba18…8e90c5

6 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity