Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d5c0b56de3c6c31ed4956af4e9e38db8e09d15400a11625daaa278ec2c14279a

Tx prefix hash: 50828c53cce355ef99b1c9efb2202e9bc81e2a920c220bebf268461c67133b07
Tx public key: ae328001647b254a6c1398fd2b926aff81be1bdd70cbfc35a6a146cb20e0c807
Timestamp: 1721418250 Timestamp [UCT]: 2024-07-19 19:44:10 Age [y:d:h:m:s]: 00:252:01:55:06
Block: 1069334 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180052 RingCT/type: yes/0
Extra: 01ae328001647b254a6c1398fd2b926aff81be1bdd70cbfc35a6a146cb20e0c807021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 541a51276e3ad19f306e6489b562a6d68555ffbd7234fbcf5266fd80fbc22de9 0.600000000000 1540715 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": 1069344, "vin": [ { "gen": { "height": 1069334 } } ], "vout": [ { "amount": 600000000, "target": { "key": "541a51276e3ad19f306e6489b562a6d68555ffbd7234fbcf5266fd80fbc22de9" } } ], "extra": [ 1, 174, 50, 128, 1, 100, 123, 37, 74, 108, 19, 152, 253, 43, 146, 106, 255, 129, 190, 27, 221, 112, 203, 252, 53, 166, 161, 70, 203, 32, 224, 200, 7, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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