Block #73,503,792

← previous blocknext block →recent activity

Analyzing

Block #73,503,792

14 transactions · 12 stateful · 2026-05-09 17:36:43 UTC

Parallelism

71/100

Blocked

42%

Avg conflicts / tx

0.5

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #73,503,792  ·  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

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0xa1087a5c…66c4

0x754704…b603

6 touches
3 conflicts

0xc9e97522…3519

0x2a68ba…90c5

6 touches
3 conflicts

0x0a6cb118…4ca3

0x1b6862…e19c

6 touches
3 conflicts

0x459eaf16…1276

0x065c9d…c394

6 touches
3 conflicts

0xfd3faf90…5c03

0xd32edf…ff58

5 touches
3 conflicts

0x00000000…0028

0x1b6862…e19c

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: 0x1b68626d…2de19c

3 conflicts on slot 0x0000000000…000013

← previous block·next block →recent activity