Block #73,696,083

← previous blocknext block →recent activity

Analyzing

Block #73,696,083

14 transactions · 12 stateful · 2026-05-10 15:02:00 UTC

Parallelism

64/100

Blocked

33%

Avg conflicts / tx

0.5

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #73,696,083  ·  14 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xc9e97522…3519

0x2a68ba…90c5

6 touches
3 conflicts

0x076d6ea8…3071

0x065c9d…c394

5 touches
3 conflicts

0x3bb0b5e8…2c32

0xd32edf…ff58

5 touches
3 conflicts

0x3a3097d7…2ab6

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

4 touches
1 conflict

0x8876d94c…8435

0x2a68ba…90c5

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

3 conflicts on slot 0xc9e9752290…9c3519

← previous block·next block →recent activity