Block #73,446,588

← previous blocknext block →recent activity

Analyzing

Block #73,446,588

32 transactions · 21 stateful · 2026-05-09 11:15:56 UTC

Parallelism

66/100

Blocked

67%

Avg conflicts / tx

1.31

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #73,446,588  ·  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

0x046a928e…0012

0x2a68ba…90c5

12 touches
15 conflicts

0xd88e1284…512e

0xd32edf…ff58

11 touches
15 conflicts

0x00000000…003d

0x065c9d…c394

10 touches
10 conflicts

0x22e295f5…1bef

0x065c9d…c394

10 touches
10 conflicts

0x4d87512b…897c

0x065c9d…c394

6 touches
3 conflicts

0x00000000…0004

0x5afd3e…7620

4 touches
1 conflict

0x4039b31f…0f4a

0x754704…b603

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

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: 0x2a68ba18…8e90c5

15 conflicts on slot 0x046a928e85…e50012

← previous block·next block →recent activity