Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c669550006c1a15f7ec849b4c066134e07baede502370d92129ddb6db39bd3fb

Tx prefix hash: 7411e9d37314ac4f12a5a9e1ee5c286e9cb4b8b85f7f44424705a7b6b3b09656
Tx public key: ae4fdcb8340f1d7cdf2a5ff4167048ac1a8eaf3303430d264cf66e26ec88ca04
Timestamp: 1707708313 Timestamp [UCT]: 2024-02-12 03:25:13 Age [y:d:h:m:s]: 00:314:17:04:59
Block: 955646 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 225344 RingCT/type: yes/0
Extra: 01ae4fdcb8340f1d7cdf2a5ff4167048ac1a8eaf3303430d264cf66e26ec88ca0402110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9cdfe5deb2b20d597b8726a5415e439c80c727241604a194f99ad864b2d50ced 0.600000000000 1414944 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": 955656, "vin": [ { "gen": { "height": 955646 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9cdfe5deb2b20d597b8726a5415e439c80c727241604a194f99ad864b2d50ced" } } ], "extra": [ 1, 174, 79, 220, 184, 52, 15, 29, 124, 223, 42, 95, 244, 22, 112, 72, 172, 26, 142, 175, 51, 3, 67, 13, 38, 76, 246, 110, 38, 236, 136, 202, 4, 2, 17, 0, 0, 0, 7, 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