Block #73,490,417

← previous blocknext block →recent activity

Analyzing

Block #73,490,417

12 transactions · 8 stateful · 2026-05-09 16:07:39 UTC

Parallelism

83/100

Blocked

13%

Avg conflicts / tx

0.08

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #73,490,417  ·  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

0xa91c899f…6ee3

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xe2616015…bb5b

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

2 touches
0 conflicts

0x22e295f5…1bef

0x065c9d…c394

2 touches
0 conflicts

0x324ec4af…c8bf

0x065c9d…c394

2 touches
0 conflicts

0x463e297c…35be

0x065c9d…c394

2 touches
0 conflicts

0x7cb60129…f71f

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: 0x34b6552d…112a6f

1 conflict on slot 0xa91c899f02…fa6ee3

← previous block·next block →recent activity