Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5a2f41bce45ef96a81f3d41b96b183eff31a9cc8f93160bf9ac712d49f723187

Tx prefix hash: 479135df074872ef4adf680a1206dce7e4116c97cafb01106e7232ab7b045190
Tx public key: 2dcb91a434a233e5caa1b8d9b010cd4e380d44e52c4efdcb90dfbb402e50adac
Timestamp: 1707565337 Timestamp [UCT]: 2024-02-10 11:42:17 Age [y:d:h:m:s]: 01:111:23:50:52
Block: 954457 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 341141 RingCT/type: yes/0
Extra: 012dcb91a434a233e5caa1b8d9b010cd4e380d44e52c4efdcb90dfbb402e50adac0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e514e752b16174cfd8ad89374683ab2e1643aa3c6ccfbb4a32225043af955e60 0.600000000000 1413737 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": 954467, "vin": [ { "gen": { "height": 954457 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e514e752b16174cfd8ad89374683ab2e1643aa3c6ccfbb4a32225043af955e60" } } ], "extra": [ 1, 45, 203, 145, 164, 52, 162, 51, 229, 202, 161, 184, 217, 176, 16, 205, 78, 56, 13, 68, 229, 44, 78, 253, 203, 144, 223, 187, 64, 46, 80, 173, 172, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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