Block #73,353,234

← previous blocknext block →recent activity

Analyzing

Block #73,353,234

14 transactions · 13 stateful · 2026-05-09 00:54:50 UTC

Parallelism

71/100

Blocked

38%

Avg conflicts / tx

0.5

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,353,234  ·  14 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

6 touches
3 conflicts

0x96504a63…52d2

0x8d66a4…3095

4 touches
1 conflict

0x9bf45045…f1a4

0x065c9d…c394

4 touches
1 conflict

0xe3c1d86e…399b

0x065c9d…c394

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x8a35acfb…d1ae

0x8d66a4…3095

4 touches
1 conflict

0xd63a62a1…daa9

0x065c9d…c394

3 touches
1 conflict

0x64ca6ba5…3a89

0x065c9d…c394

3 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

3 conflicts on slot 0xf2f76ab392…f3623e

← previous block·next block →recent activity