Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 579e4bd7f54549c10c33f4df731dc72f4205181d2c8ef016e1defcccf0533108

Tx prefix hash: 7a5dfff0aaf7a9e4b5264ffdc1df6a1e74ed81bab92c719888117f4a0c518be8
Tx public key: a9ff7760a58476fe763a38dcc0057234759266c43575b8664767c503e8a1d6f4
Timestamp: 1717648126 Timestamp [UCT]: 2024-06-06 04:28:46 Age [y:d:h:m:s]: 01:213:08:51:38
Block: 1038056 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 411149 RingCT/type: yes/0
Extra: 01a9ff7760a58476fe763a38dcc0057234759266c43575b8664767c503e8a1d6f40211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aac3245038952fcf856b3b05fe980412d7f4f84a1edaf7211d5fdab32eaadec2 0.600000000000 1506615 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": 1038066, "vin": [ { "gen": { "height": 1038056 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aac3245038952fcf856b3b05fe980412d7f4f84a1edaf7211d5fdab32eaadec2" } } ], "extra": [ 1, 169, 255, 119, 96, 165, 132, 118, 254, 118, 58, 56, 220, 192, 5, 114, 52, 117, 146, 102, 196, 53, 117, 184, 102, 71, 103, 197, 3, 232, 161, 214, 244, 2, 17, 0, 0, 0, 3, 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