Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 310cb05d10d06e4ae7da27db29d1582c19e6574c53c458a8a7679db8a26f1f43

Tx prefix hash: 9a5f4543c2f1e6b441c8b93afeb043240408edcd20f84bd997e3b62a2f13eede
Tx public key: 663b409097245f07c8d1942d025e98dc8c21d31c5f08ae1d8bd854d9ad265cba
Timestamp: 1710769341 Timestamp [UCT]: 2024-03-18 13:42:21 Age [y:d:h:m:s]: 01:057:01:17:53
Block: 981048 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 301775 RingCT/type: yes/0
Extra: 01663b409097245f07c8d1942d025e98dc8c21d31c5f08ae1d8bd854d9ad265cba021100000001679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1cd5f44f8a73ae62f5e9eb84c14f6bf7aad4a7cf3820b60709479257c7d8b721 0.600000000000 1441133 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": 981058, "vin": [ { "gen": { "height": 981048 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1cd5f44f8a73ae62f5e9eb84c14f6bf7aad4a7cf3820b60709479257c7d8b721" } } ], "extra": [ 1, 102, 59, 64, 144, 151, 36, 95, 7, 200, 209, 148, 45, 2, 94, 152, 220, 140, 33, 211, 28, 95, 8, 174, 29, 139, 216, 84, 217, 173, 38, 92, 186, 2, 17, 0, 0, 0, 1, 103, 154, 138, 129, 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