Block #73,324,452

← previous blocknext block →recent activity

Analyzing

Block #73,324,452

25 transactions · 22 stateful · 2026-05-08 21:43:20 UTC

Parallelism

64/100

Blocked

45%

Avg conflicts / tx

1.48

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #73,324,452  ·  25 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x046a928e…0012

0x2a68ba…90c5

12 touches
15 conflicts

0xbd7e37a9…9eb5

0x065c9d…c394

8 touches
6 conflicts

0x0b390c61…dc07

0x065c9d…c394

6 touches
3 conflicts

0xd821ae10…fe17

0xc8689a…ee79

4 touches
1 conflict

0x16d1eda9…6c59

0x065c9d…c394

4 touches
1 conflict

0x1c234d14…c743

0x065c9d…c394

4 touches
1 conflict

0xd98b3c10…67b8

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: 0x065c9d28…a9c394

21 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity