Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: edf1c2ec2937040b7b6f36e49cceb0bdf100f9e488e6589a18f384f90206ea53

Tx prefix hash: a02a014ebb975bbdc0af91de6f7e79311725338f5dd638b3a7d9194de8b9748b
Tx public key: 1239c2969d2f7e150b8dac6d96b19c79d0c49119f3ff0ce1fc225337291f71fe
Timestamp: 1713765806 Timestamp [UCT]: 2024-04-22 06:03:26 Age [y:d:h:m:s]: 00:361:02:11:37
Block: 1005868 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 258148 RingCT/type: yes/0
Extra: 011239c2969d2f7e150b8dac6d96b19c79d0c49119f3ff0ce1fc225337291f71fe0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 50535c17b10feef436615a99788ce8e88acf591f466e0771a03e3c51e27d2469 0.600000000000 1466700 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": 1005878, "vin": [ { "gen": { "height": 1005868 } } ], "vout": [ { "amount": 600000000, "target": { "key": "50535c17b10feef436615a99788ce8e88acf591f466e0771a03e3c51e27d2469" } } ], "extra": [ 1, 18, 57, 194, 150, 157, 47, 126, 21, 11, 141, 172, 109, 150, 177, 156, 121, 208, 196, 145, 25, 243, 255, 12, 225, 252, 34, 83, 55, 41, 31, 113, 254, 2, 17, 0, 0, 0, 2, 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