Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cdff837ecbf2a1a8d480ce4174be3e6d8c939f91c026efcbeb4c80b94f71da02

Tx prefix hash: 61da8501ef411f325d0985b7daef84a904e84666b7afb144ff0967df704ca731
Tx public key: d5bc0842beacadef8d036ef83bd00d9ac5a892d4f4c12fd9993a7efac30a76a6
Timestamp: 1732224754 Timestamp [UCT]: 2024-11-21 21:32:34 Age [y:d:h:m:s]: 00:002:10:13:53
Block: 1158806 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1742 RingCT/type: yes/0
Extra: 01d5bc0842beacadef8d036ef83bd00d9ac5a892d4f4c12fd9993a7efac30a76a6021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6ace3294cd65e14682c55d35e925f4e073d61969f148f2dec668928ccf21768c 0.600000000000 1644435 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": 1158816, "vin": [ { "gen": { "height": 1158806 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6ace3294cd65e14682c55d35e925f4e073d61969f148f2dec668928ccf21768c" } } ], "extra": [ 1, 213, 188, 8, 66, 190, 172, 173, 239, 141, 3, 110, 248, 59, 208, 13, 154, 197, 168, 146, 212, 244, 193, 47, 217, 153, 58, 126, 250, 195, 10, 118, 166, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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