Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed634f258f5f0a4e16ba2cd39292ddc9ca7181dffd51eaae9dcba5f526e9d252

Tx prefix hash: fc65ddb79aa5e76bf3f444b876dff1bc5f8c53fee9fd1eeadf1b3a025135848d
Tx public key: cdbcc8c7e6f598b9660454abd900b1571ad125628eb795bb371dca31d25ab0fd
Timestamp: 1729731311 Timestamp [UCT]: 2024-10-24 00:55:11 Age [y:d:h:m:s]: 00:142:13:51:52
Block: 1138202 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101711 RingCT/type: yes/0
Extra: 01cdbcc8c7e6f598b9660454abd900b1571ad125628eb795bb371dca31d25ab0fd02110000000d1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 956778fe98337671b072009441d0875ac4faedeeaa41e4c193fe0a0b76c32514 0.600000000000 1621821 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": 1138212, "vin": [ { "gen": { "height": 1138202 } } ], "vout": [ { "amount": 600000000, "target": { "key": "956778fe98337671b072009441d0875ac4faedeeaa41e4c193fe0a0b76c32514" } } ], "extra": [ 1, 205, 188, 200, 199, 230, 245, 152, 185, 102, 4, 84, 171, 217, 0, 177, 87, 26, 209, 37, 98, 142, 183, 149, 187, 55, 29, 202, 49, 210, 90, 176, 253, 2, 17, 0, 0, 0, 13, 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