Block #73,469,213

← previous blocknext block →recent activity

Analyzing

Block #73,469,213

11 transactions · 10 stateful · 2026-05-09 13:46:32 UTC

Parallelism

45/100

Blocked

60%

Avg conflicts / tx

2

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #73,469,213  ·  11 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

0xf2f76ab3…623e

0x2a68ba…90c5

12 touches
15 conflicts

0x00000000…003d

0x065c9d…c394

10 touches
10 conflicts

0x6f08361d…bda6

0x065c9d…c394

8 touches
6 conflicts

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x1f812c3b…72b0

0x065c9d…c394

2 touches
0 conflicts

0x20369078…ee42

0x065c9d…c394

2 touches
0 conflicts

0x4f47c431…b8b7

0x065c9d…c394

2 touches
0 conflicts

0x7f49bbf1…6327

0x065c9d…c394

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

15 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity