Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf0e9acb50a44ca8c856b8a906e9c7f2fc2d892ebcfae38ffb15f2eaba4cd480

Tx prefix hash: f03af32843c69407b7c54a2d7015e52210c0ee29b92ecbfa5e4535055fd94760
Tx public key: a17c6e376da032f16817fff663964246639a0343b80feecfe3eb8fcb3325e14c
Timestamp: 1740606411 Timestamp [UCT]: 2025-02-26 21:46:51 Age [y:d:h:m:s]: 00:172:21:26:36
Block: 1227927 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 121442 RingCT/type: yes/0
Extra: 01a17c6e376da032f16817fff663964246639a0343b80feecfe3eb8fcb3325e14c0211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 37e78e450e047d0a9335ffb8edb21dd44a5b3244bb9c249c15558d89b934cf85 0.600000000000 1714802 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": 1227937, "vin": [ { "gen": { "height": 1227927 } } ], "vout": [ { "amount": 600000000, "target": { "key": "37e78e450e047d0a9335ffb8edb21dd44a5b3244bb9c249c15558d89b934cf85" } } ], "extra": [ 1, 161, 124, 110, 55, 109, 160, 50, 241, 104, 23, 255, 246, 99, 150, 66, 70, 99, 154, 3, 67, 184, 15, 238, 207, 227, 235, 143, 203, 51, 37, 225, 76, 2, 17, 0, 0, 0, 6, 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