Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0cbcc7e22960ec18282e86ca7355e1ccd5710964dddc5d0de1c13d5a6fab514f

Tx prefix hash: 72d2a79e28eb0f1269a749fb68f05bd31acb96017702437dbb68fc8a734eac0d
Tx public key: dc58774aecc8e1ea3b01380effbf2894f8ff91d5c3c517ad59bf013f07b156f8
Timestamp: 1712384149 Timestamp [UCT]: 2024-04-06 06:15:49 Age [y:d:h:m:s]: 01:006:13:21:00
Block: 994385 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 265670 RingCT/type: yes/0
Extra: 01dc58774aecc8e1ea3b01380effbf2894f8ff91d5c3c517ad59bf013f07b156f802110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1665644188497eab0f2ffab45c3e88841a45bdba8fbfb9e5f7892c03822a8670 0.600000000000 1454787 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": 994395, "vin": [ { "gen": { "height": 994385 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1665644188497eab0f2ffab45c3e88841a45bdba8fbfb9e5f7892c03822a8670" } } ], "extra": [ 1, 220, 88, 119, 74, 236, 200, 225, 234, 59, 1, 56, 14, 255, 191, 40, 148, 248, 255, 145, 213, 195, 197, 23, 173, 89, 191, 1, 63, 7, 177, 86, 248, 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