Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9c422d3faadfe6e53a33da7ae468a0c9b44e238dc966d826fba6bc82da8eae4e

Tx prefix hash: b2bd9a52e6a8bfa7022a8793e4c77803f52e5c1c0808b36cc2a5ad6a3dde0c5a
Tx public key: 6015336f59c222d444c2e7e5ad6309dd93cd9eefcfebaaef90345a955766faf1
Timestamp: 1714394427 Timestamp [UCT]: 2024-04-29 12:40:27 Age [y:d:h:m:s]: 00:304:01:16:46
Block: 1011080 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 217330 RingCT/type: yes/0
Extra: 016015336f59c222d444c2e7e5ad6309dd93cd9eefcfebaaef90345a955766faf10211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c97c7b4b3876235119fe9b69bbec7a0e80b070ce0aed00ce374313436b6b2cd5 0.600000000000 1473212 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": 1011090, "vin": [ { "gen": { "height": 1011080 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c97c7b4b3876235119fe9b69bbec7a0e80b070ce0aed00ce374313436b6b2cd5" } } ], "extra": [ 1, 96, 21, 51, 111, 89, 194, 34, 212, 68, 194, 231, 229, 173, 99, 9, 221, 147, 205, 158, 239, 207, 235, 170, 239, 144, 52, 90, 149, 87, 102, 250, 241, 2, 17, 0, 0, 0, 1, 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