Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c82e84e739c5460699e94b7e9a0cd74c22a910b2adf11819b789a9db90e6747

Tx prefix hash: 18a09e03ced957d9c7d9a68d0bd6e90bae6c4fc145acddd9e066128fa9fbc2af
Tx public key: 86729673d36d63f4cd857e14d27cfd5fb0115b1bec2156729d03f2bb972b2594
Timestamp: 1709741961 Timestamp [UCT]: 2024-03-06 16:19:21 Age [y:d:h:m:s]: 01:034:16:52:56
Block: 972520 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 285795 RingCT/type: yes/0
Extra: 0186729673d36d63f4cd857e14d27cfd5fb0115b1bec2156729d03f2bb972b259402110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae75802bcb04727e1230f0728ed3c9e4dcc06c5372c284bc1eca1ef852be83f9 0.600000000000 1432435 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": 972530, "vin": [ { "gen": { "height": 972520 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae75802bcb04727e1230f0728ed3c9e4dcc06c5372c284bc1eca1ef852be83f9" } } ], "extra": [ 1, 134, 114, 150, 115, 211, 109, 99, 244, 205, 133, 126, 20, 210, 124, 253, 95, 176, 17, 91, 27, 236, 33, 86, 114, 157, 3, 242, 187, 151, 43, 37, 148, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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