Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd819b0941f9dea32efdbc31147d4cb7d76344351e86341d5135e0baf7c616fc

Tx prefix hash: 8625e2205f61ff71cc21af98449af2fa71d1f6a055458479394c4da7033cadfd
Tx public key: edd964a70355edec7713cb04e679e78d70e74083c9f30eee3139ff64e2efc14b
Timestamp: 1695529325 Timestamp [UCT]: 2023-09-24 04:22:05 Age [y:d:h:m:s]: 01:196:15:25:03
Block: 854878 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 401592 RingCT/type: yes/0
Extra: 01edd964a70355edec7713cb04e679e78d70e74083c9f30eee3139ff64e2efc14b02110000000c4b8f5122000000000000000000

1 output(s) for total of 0.902473293000 dcy

stealth address amount amount idx
00: b0cc67eb1db6ec2c81416a6038043afccd2aae6c278a4526c8a0184ead897cdc 0.902473293000 1308870 of 0

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": 854888, "vin": [ { "gen": { "height": 854878 } } ], "vout": [ { "amount": 902473293, "target": { "key": "b0cc67eb1db6ec2c81416a6038043afccd2aae6c278a4526c8a0184ead897cdc" } } ], "extra": [ 1, 237, 217, 100, 167, 3, 85, 237, 236, 119, 19, 203, 4, 230, 121, 231, 141, 112, 231, 64, 131, 201, 243, 14, 238, 49, 57, 255, 100, 226, 239, 193, 75, 2, 17, 0, 0, 0, 12, 75, 143, 81, 34, 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