Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 9fee4b731aade4158488f133d388f5ad13d095f1c50ac0b441c6ed8f96a0a388

Tx prefix hash: ace76c94e675de38c741afdd7f242ae77b5f2f8b6aa201bce8551fd82a56b6d7
Tx public key: 494810fa880565c447d0536562463411fd10118d611a0d91eb1f953cc96a01da
Timestamp: 1712424521 Timestamp [UCT]: 2024-04-06 17:28:41 Age [y:d:h:m:s]: 01:244:00:43:35
Block: 994717 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 433149 RingCT/type: yes/0
Extra: 01494810fa880565c447d0536562463411fd10118d611a0d91eb1f953cc96a01da02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 46ad2c387e95f908de553011d20996c2fd27c87350fd4dfd7d166b6ae5e59f34 0.600000000000 1455121 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 994727, "vin": [ { "gen": { "height": 994717 } } ], "vout": [ { "amount": 600000000, "target": { "key": "46ad2c387e95f908de553011d20996c2fd27c87350fd4dfd7d166b6ae5e59f34" } } ], "extra": [ 1, 73, 72, 16, 250, 136, 5, 101, 196, 71, 208, 83, 101, 98, 70, 52, 17, 253, 16, 17, 141, 97, 26, 13, 145, 235, 31, 149, 60, 201, 106, 1, 218, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8