Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5a1d7d8d52d09ca9c6902efe4a32e9fbebd7291e153c14ebd9b41d614f505968

Tx prefix hash: 5853c5714af4bba473e387b117c2cf016bbfdbdb4bebca62791153d8dda3f6a9
Tx public key: cd5eb47ed1c42e335ea1eebe911b64d2c61fea186c984f215e36870b7c048988
Timestamp: 1668611571 Timestamp [UCT]: 2022-11-16 15:12:51 Age [y:d:h:m:s]: 02:008:14:48:51
Block: 632450 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 528041 RingCT/type: yes/0
Extra: 01cd5eb47ed1c42e335ea1eebe911b64d2c61fea186c984f215e36870b7c048988021100000001faf35c9c000000000000000000

1 output(s) for total of 4.925276539000 dcy

stealth address amount amount idx
00: efc6399b7a7b6e5a31b86b02fb14ae2c5377dcfc6f92c2143cf5efa3c269b873 4.925276539000 1071397 of 0

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": 632460, "vin": [ { "gen": { "height": 632450 } } ], "vout": [ { "amount": 4925276539, "target": { "key": "efc6399b7a7b6e5a31b86b02fb14ae2c5377dcfc6f92c2143cf5efa3c269b873" } } ], "extra": [ 1, 205, 94, 180, 126, 209, 196, 46, 51, 94, 161, 238, 190, 145, 27, 100, 210, 198, 31, 234, 24, 108, 152, 79, 33, 94, 54, 135, 11, 124, 4, 137, 136, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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