Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf9313665aa932a6be849677470514c8ac41058eb1d78f1dc76d4af8558c6b57

Tx prefix hash: 83cd05c5ee251f24082cfc2d68329cf77db1eccbf6d2ffad467a98e3e99ceb9f
Tx public key: 1f0db4e23d4c7b60b205243b49490e85e88160044329e37102b28cd48b0fb227
Timestamp: 1722299452 Timestamp [UCT]: 2024-07-30 00:30:52 Age [y:d:h:m:s]: 00:163:02:14:29
Block: 1076614 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116694 RingCT/type: yes/0
Extra: 011f0db4e23d4c7b60b205243b49490e85e88160044329e37102b28cd48b0fb22702110000001291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1c883a7c7ee0ba3d14aeecdddde19940f494b06ad9d773c3466c788ee0b166b8 0.600000000000 1549153 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": 1076624, "vin": [ { "gen": { "height": 1076614 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1c883a7c7ee0ba3d14aeecdddde19940f494b06ad9d773c3466c788ee0b166b8" } } ], "extra": [ 1, 31, 13, 180, 226, 61, 76, 123, 96, 178, 5, 36, 59, 73, 73, 14, 133, 232, 129, 96, 4, 67, 41, 227, 113, 2, 178, 140, 212, 139, 15, 178, 39, 2, 17, 0, 0, 0, 18, 145, 225, 60, 4, 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