Block #73,594,319

← previous blocknext block →recent activity

Analyzing

Block #73,594,319

22 transactions · 16 stateful · 2026-05-10 03:38:09 UTC

Parallelism

68/100

Blocked

44%

Avg conflicts / tx

1

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #73,594,319  ·  22 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xc385fabb…2c33

0xd32edf…ff58

13 touches
21 conflicts

0x6ea8fa8d…3dd6

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0002

0xab3526…fa38

4 touches
1 conflict

0xa1826e77…1e5a

0x065c9d…c394

2 touches
0 conflicts

0xc9e97522…3519

0x2a68ba…90c5

2 touches
0 conflicts

0x7c403af1…31b1

0x3bd359…433a

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

21 conflicts on slot 0xc385fabb45…892c33

← previous block·next block →recent activity