Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a4492100aae54b2e09d74af697041b55b37ef8a737c7cca9c83af6b36c9f65b7

Tx prefix hash: 645f55f1acaf0c00d6ffa6ecd3573e5c6158f286a12678f44c42b0ac0a80734b
Tx public key: 0f6859d1456daceeba97e946531a9dc043eacfad84f80fd1bdd331ba7ca8f3de
Timestamp: 1706971951 Timestamp [UCT]: 2024-02-03 14:52:31 Age [y:d:h:m:s]: 01:079:20:41:58
Block: 949527 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 318157 RingCT/type: yes/0
Extra: 010f6859d1456daceeba97e946531a9dc043eacfad84f80fd1bdd331ba7ca8f3de02110000000d59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e8f871cdea37d05ad0c4311e114687d9a396fb4f4f4c59cda0446a89dc3ca56b 0.600000000000 1408053 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": 949537, "vin": [ { "gen": { "height": 949527 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e8f871cdea37d05ad0c4311e114687d9a396fb4f4f4c59cda0446a89dc3ca56b" } } ], "extra": [ 1, 15, 104, 89, 209, 69, 109, 172, 238, 186, 151, 233, 70, 83, 26, 157, 192, 67, 234, 207, 173, 132, 248, 15, 209, 189, 211, 49, 186, 124, 168, 243, 222, 2, 17, 0, 0, 0, 13, 89, 218, 211, 245, 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