Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4aaf038fd34dd04c0926b35a6aae634bfb7aa4f2f86c187928f1082f7f94e913

Tx prefix hash: 291116bf968c519a7aff59635bc38da69ebd2e6d91f57ab0aee82da7713fc8b8
Tx public key: 61a1c807cb58e10a70005d87a716a41bc230c8815524f40cb4e647c3b504a679
Timestamp: 1733721752 Timestamp [UCT]: 2024-12-09 05:22:32 Age [y:d:h:m:s]: 00:121:23:57:12
Block: 1171212 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 86991 RingCT/type: yes/0
Extra: 0161a1c807cb58e10a70005d87a716a41bc230c8815524f40cb4e647c3b504a679021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4365681b24c01dc108bc5c8ea934577527b232d0714e9964e8d874fe9bbc6787 0.600000000000 1656951 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": 1171222, "vin": [ { "gen": { "height": 1171212 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4365681b24c01dc108bc5c8ea934577527b232d0714e9964e8d874fe9bbc6787" } } ], "extra": [ 1, 97, 161, 200, 7, 203, 88, 225, 10, 112, 0, 93, 135, 167, 22, 164, 27, 194, 48, 200, 129, 85, 36, 244, 12, 180, 230, 71, 195, 181, 4, 166, 121, 2, 17, 0, 0, 0, 3, 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