Block #73,649,114

← previous blocknext block →recent activity

Analyzing

Block #73,649,114

13 transactions · 10 stateful · 2026-05-10 09:45:12 UTC

Parallelism

77/100

Blocked

40%

Avg conflicts / tx

0.38

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #73,649,114  ·  13 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

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x5450fbe1…9082

0x065c9d…c394

6 touches
3 conflicts

0xae69c125…2379

0x2a68ba…90c5

6 touches
3 conflicts

0x00000000…000b

0x6c4bfa…a540

6 touches
3 conflicts

0xf0f673fd…37a7

0x6c4bfa…a540

6 touches
3 conflicts

0xed57bddf…1abf

0xc8689a…ee79

6 touches
3 conflicts

0x03bd7b33…9ecf

0x065c9d…c394

5 touches
3 conflicts

0x2e2214a9…fe0d

0x6c4bfa…a540

5 touches
3 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: 0x065c9d28…a9c394

3 conflicts on slot 0x0000000000…00003d

← previous block·next block →recent activity