Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 449c0ab991cd872a9a3fb06f1efe2455aab9e3ba084f5f9d679072d1d6c3bf00

Tx prefix hash: 7167ea6bde289178dee65367d6a9f5b30aa8e24a72a46db9becfec1680185a2d
Tx public key: 83c7fdee43224c503d1fd19d0eae86920cab877d433e93cff9e5aa45c737e184
Timestamp: 1719200563 Timestamp [UCT]: 2024-06-24 03:42:43 Age [y:d:h:m:s]: 00:356:17:17:19
Block: 1050920 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 254862 RingCT/type: yes/0
Extra: 0183c7fdee43224c503d1fd19d0eae86920cab877d433e93cff9e5aa45c737e18402110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d906dc515d0d642c6a8e5dc7ea0af6e5347146ef1bb0aa1595809b0152b56974 0.600000000000 1521097 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": 1050930, "vin": [ { "gen": { "height": 1050920 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d906dc515d0d642c6a8e5dc7ea0af6e5347146ef1bb0aa1595809b0152b56974" } } ], "extra": [ 1, 131, 199, 253, 238, 67, 34, 76, 80, 61, 31, 209, 157, 14, 174, 134, 146, 12, 171, 135, 125, 67, 62, 147, 207, 249, 229, 170, 69, 199, 55, 225, 132, 2, 17, 0, 0, 0, 1, 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