Block #73,493,147

← previous blocknext block →recent activity

Analyzing

Block #73,493,147

18 transactions · 14 stateful · 2026-05-09 16:25:47 UTC

Parallelism

67/100

Blocked

36%

Avg conflicts / tx

1.06

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,493,147  ·  18 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

12 touches
15 conflicts

0x046a928e…0012

0x2a68ba…90c5

10 touches
10 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x4d87512b…897c

0x065c9d…c394

2 touches
0 conflicts

0x9b675023…d916

0x065c9d…c394

2 touches
0 conflicts

0xc8cabf9b…2745

0x065c9d…c394

2 touches
0 conflicts

0x00000000…0012

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…0018

0x1b6862…e19c

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

15 conflicts on slot 0x22e295f5d8…ac1bef

← previous block·next block →recent activity