Block #73,492,411

← previous blocknext block →recent activity

Analyzing

Block #73,492,411

8 transactions · 7 stateful · 2026-05-09 16:20:56 UTC

Parallelism

75/100

Blocked

14%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,492,411  ·  8 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

0x02068a29…2f8b

0x065c9d…c394

2 touches
0 conflicts

0x0443e663…d1e8

0x065c9d…c394

2 touches
0 conflicts

0x2973d035…ee36

0x065c9d…c394

2 touches
0 conflicts

0x37fac5a6…8c21

0x065c9d…c394

2 touches
0 conflicts

0x67f5219f…4ff3

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

← previous block·next block →recent activity