Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d60c0fd0cc344232cf065e787f9765f7fb771ad61c6b8e443981c231f8cc50da

Tx prefix hash: 839bcfb54b616ec56a8574b5aa5c09b4c0c6c20710209ae9e8e04b4cb5248923
Tx public key: 3c54ee6236ebc6665d1915d267376d85cb9f64720f52d935a93696df12067281
Timestamp: 1704359110 Timestamp [UCT]: 2024-01-04 09:05:10 Age [y:d:h:m:s]: 01:334:21:40:36
Block: 927886 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 498206 RingCT/type: yes/0
Extra: 013c54ee6236ebc6665d1915d267376d85cb9f64720f52d935a93696df12067281021100000005c5452960000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2bfc9454b6e502f3741bc830ccf3c2401da3d0fbcfcafe79e75b3b48568cf9d0 0.600000000000 1385728 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": 927896, "vin": [ { "gen": { "height": 927886 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2bfc9454b6e502f3741bc830ccf3c2401da3d0fbcfcafe79e75b3b48568cf9d0" } } ], "extra": [ 1, 60, 84, 238, 98, 54, 235, 198, 102, 93, 25, 21, 210, 103, 55, 109, 133, 203, 159, 100, 114, 15, 82, 217, 53, 169, 54, 150, 223, 18, 6, 114, 129, 2, 17, 0, 0, 0, 5, 197, 69, 41, 96, 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