Block #73,374,901

← previous blocknext block →recent activity

Analyzing

Block #73,374,901

32 transactions · 26 stateful · 2026-05-09 03:18:53 UTC

Parallelism

66/100

Blocked

54%

Avg conflicts / tx

1.47

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #73,374,901  ·  32 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0x00000000…003d

0x065c9d…c394

14 touches
21 conflicts

0xf2f76ab3…623e

0x2a68ba…90c5

12 touches
15 conflicts

0x4d87512b…897c

0x065c9d…c394

12 touches
15 conflicts

0x3ae9a1a3…48b0

0xd32edf…ff58

9 touches
10 conflicts

0x22e295f5…1bef

0x065c9d…c394

8 touches
6 conflicts

0x1d342098…425d

0x065c9d…c394

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

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

21 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity