Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 47de556533fa0744769c0b86f0575d85fd318da114c02aec3e3f73e6c5cdb208

Tx prefix hash: 16d0ee6c1ccd4570caa812b51edd4b9fc016c793635611db78dd05a5134ceda4
Tx public key: d3c3b0e0b185da1ed935e76a96353bafd2ad2853f3739e71366adb145b0b6b66
Timestamp: 1740700540 Timestamp [UCT]: 2025-02-27 23:55:40 Age [y:d:h:m:s]: 00:314:17:54:16
Block: 1228700 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 222793 RingCT/type: yes/0
Extra: 01d3c3b0e0b185da1ed935e76a96353bafd2ad2853f3739e71366adb145b0b6b6602110000000c1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ccbf2422a172bd6e6a07292301e3edc4c833bd846b7e97ef3bc77f478691843d 0.600000000000 1715581 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": 1228710, "vin": [ { "gen": { "height": 1228700 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ccbf2422a172bd6e6a07292301e3edc4c833bd846b7e97ef3bc77f478691843d" } } ], "extra": [ 1, 211, 195, 176, 224, 177, 133, 218, 30, 217, 53, 231, 106, 150, 53, 59, 175, 210, 173, 40, 83, 243, 115, 158, 113, 54, 106, 219, 20, 91, 11, 107, 102, 2, 17, 0, 0, 0, 12, 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