← previous blocknext block →recent activity

Analyzing

Block #73,533,574

9 transactions · 9 stateful · 2026-05-09 20:54:38 UTC

Parallelism

67/100

Blocked

22%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,533,574  ·  9 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

4 touches
1 conflict

0x22e295f5…1bef

0x065c9d…c394

4 touches
1 conflict

0xd2073fe4…d490

0x065c9d…c394

4 touches
1 conflict

0xd8f41a78…ce25

0x065c9d…c394

3 touches
1 conflict

0x2f692b95…7318

0x065c9d…c394

3 touches
1 conflict

0xe0b7bc17…9f33

0x065c9d…c394

3 touches
1 conflict

0xa408148f…3b64

0x065c9d…c394

3 touches
1 conflict

0x00000000…0029

0x1b6862…e19c

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

1 conflict on slot 0x046a928e85…e50012

← previous block·next block →recent activity