Block #73,328,306

← previous blocknext block →recent activity

Analyzing

Block #73,328,306

36 transactions · 27 stateful · 2026-05-08 22:09:02 UTC

Parallelism

61/100

Blocked

63%

Avg conflicts / tx

2.69

Longest chain

14 deep

Execution timeline

did this block parallelize well?

view

block #73,328,306  ·  36 txs across 14 waves  ·  depth 14
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

wave w12

wave w13

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

0xde421278…0634

0xd32edf…ff58

27 touches
91 conflicts

0xf537eaa0…73c8

0x065c9d…c394

6 touches
3 conflicts

0x046a928e…0012

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…001d

0x1b6862…e19c

4 touches
1 conflict

0xada193dc…5c7e

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x9ea57326…329f

0x34b655…2a6f

4 touches
1 conflict

0xcbf04108…7fb4

0x34b655…2a6f

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: 0xd32edf66…9fff58

91 conflicts on slot 0xde4212781f…c90634

← previous block·next block →recent activity