Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 63479b9c54767007de1ad652b273edd6977723f4c95ad2637d63b009e1e08a9d

Tx prefix hash: 0dd3538de94c1fdd36e6ef362567c32a33becf4d836a1dadc92eaea9b6fdf802
Tx public key: 1b15fd89e700687f11dede2d0c113429f914c15bd342be6d2998d41761ad5ad5
Timestamp: 1730781043 Timestamp [UCT]: 2024-11-05 04:30:43 Age [y:d:h:m:s]: 00:144:09:38:27
Block: 1146842 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103033 RingCT/type: yes/0
Extra: 011b15fd89e700687f11dede2d0c113429f914c15bd342be6d2998d41761ad5ad5021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9eb3ebe85d96391ca6295cc3b258797d4c0aeda628eb1d444e8e9b6ebc1b49fe 0.600000000000 1631533 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": 1146852, "vin": [ { "gen": { "height": 1146842 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9eb3ebe85d96391ca6295cc3b258797d4c0aeda628eb1d444e8e9b6ebc1b49fe" } } ], "extra": [ 1, 27, 21, 253, 137, 231, 0, 104, 127, 17, 222, 222, 45, 12, 17, 52, 41, 249, 20, 193, 91, 211, 66, 190, 109, 41, 152, 212, 23, 97, 173, 90, 213, 2, 17, 0, 0, 0, 7, 0, 127, 151, 138, 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