Block #73,375,012

← previous blocknext block →recent activity

Analyzing

Block #73,375,012

22 transactions · 18 stateful · 2026-05-09 03:19:37 UTC

Parallelism

73/100

Blocked

61%

Avg conflicts / tx

1.45

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,375,012  ·  22 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

0x4d87512b…897c

0x065c9d…c394

10 touches
10 conflicts

0xc3c8642a…7da5

0x2a68ba…90c5

8 touches
6 conflicts

0xa1087a5c…66c4

0x754704…b603

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

8 touches
6 conflicts

0x40600bc2…67d8

0xd32edf…ff58

7 touches
6 conflicts

0xecd87a39…d9c5

0x34b655…2a6f

6 touches
3 conflicts

0xfe39a1f7…8eb0

0x34b655…2a6f

6 touches
3 conflicts

0xb5cfe5ac…20b4

0x3bd359…433a

6 touches
3 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

10 conflicts on slot 0x4d87512b00…43897c

← previous block·next block →recent activity