Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ea50b64b9a17b072e9e3563e350fe26ae6388b6e6cba8a70418a309687f84f37

Tx prefix hash: 794d6ec2c2671bfcf2fced2ac642a663f96b096bbdc1c4842553d649794769f5
Tx public key: a1fa771b6129e19d59afc58892e6dd1a11320640a2debcb9d59f8d42b9cceace
Timestamp: 1719988223 Timestamp [UCT]: 2024-07-03 06:30:23 Age [y:d:h:m:s]: 01:123:17:10:17
Block: 1057463 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 346933 RingCT/type: yes/0
Extra: 01a1fa771b6129e19d59afc58892e6dd1a11320640a2debcb9d59f8d42b9cceace021100000001341001ae000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d80747fedf660b8cf007873edc320f65b0af3c62511e39aa088289f31f3a1b9d 0.600000000000 1527898 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": 1057473, "vin": [ { "gen": { "height": 1057463 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d80747fedf660b8cf007873edc320f65b0af3c62511e39aa088289f31f3a1b9d" } } ], "extra": [ 1, 161, 250, 119, 27, 97, 41, 225, 157, 89, 175, 197, 136, 146, 230, 221, 26, 17, 50, 6, 64, 162, 222, 188, 185, 213, 159, 141, 66, 185, 204, 234, 206, 2, 17, 0, 0, 0, 1, 52, 16, 1, 174, 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