Block #73,501,044

← previous blocknext block →recent activity

Analyzing

Block #73,501,044

16 transactions · 13 stateful · 2026-05-09 17:18:20 UTC

Parallelism

69/100

Blocked

46%

Avg conflicts / tx

0.56

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,501,044  ·  16 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

0xdc3306da…83e0

0x065c9d…c394

6 touches
3 conflicts

0xae69c125…2379

0x2a68ba…90c5

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0x2a7215c7…bd05

0xd32edf…ff58

5 touches
3 conflicts

0x00000000…0018

0x1b6862…e19c

4 touches
1 conflict

0xcb45d9d6…cb80

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x22e295f5…1bef

0x065c9d…c394

4 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

3 conflicts on slot 0xdc3306da26…1b83e0

← previous block·next block →recent activity