Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 835cf4fe20cac3a21fb934023616d6d02cc0aacfbc1ac7987ee8eac0dc0ded95

Tx prefix hash: 29f2564b61e77c3297d7a776c7e6f6335913f85b9a9a44c9ed06404dcef97e64
Tx public key: f8ebd9b74c10e8486c477f8f4dd0df69e4180a7dc7b5b2d28ebc3e64f46415ed
Timestamp: 1735234211 Timestamp [UCT]: 2024-12-26 17:30:11 Age [y:d:h:m:s]: 00:085:15:49:35
Block: 1183728 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 61013 RingCT/type: yes/0
Extra: 01f8ebd9b74c10e8486c477f8f4dd0df69e4180a7dc7b5b2d28ebc3e64f46415ed0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9e7c9b3b374d30e6990ed6162f18c560e44c1609c807a7aa0bac9d788475cbca 0.600000000000 1670177 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": 1183738, "vin": [ { "gen": { "height": 1183728 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9e7c9b3b374d30e6990ed6162f18c560e44c1609c807a7aa0bac9d788475cbca" } } ], "extra": [ 1, 248, 235, 217, 183, 76, 16, 232, 72, 108, 71, 127, 143, 77, 208, 223, 105, 228, 24, 10, 125, 199, 181, 178, 210, 142, 188, 62, 100, 244, 100, 21, 237, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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