Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0814e3aead25c3837f83a15d60c3c10ae25e2c28c6c28dba9fff03ccd56d2d56

Tx prefix hash: 606eb8c9956a921e28b3aa34be668a4d82ab2c57923be94a074b07168f414651
Tx public key: baa078078ff348e3d28f145c9133b3c1b458e88c1593bd4fa6fbc256b708e8c1
Timestamp: 1581365671 Timestamp [UCT]: 2020-02-10 20:14:31 Age [y:d:h:m:s]: 04:323:12:04:54
Block: 62285 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1123312 RingCT/type: yes/0
Extra: 01baa078078ff348e3d28f145c9133b3c1b458e88c1593bd4fa6fbc256b708e8c1021100000003d81c26c0000000000000000000

1 output(s) for total of 381.614400049000 dcy

stealth address amount amount idx
00: cc803600e508ce42f8b39f37660e2bc25faed55fc9d34c75477ab3ccd8003423 381.614400049000 114858 of 0

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": 62295, "vin": [ { "gen": { "height": 62285 } } ], "vout": [ { "amount": 381614400049, "target": { "key": "cc803600e508ce42f8b39f37660e2bc25faed55fc9d34c75477ab3ccd8003423" } } ], "extra": [ 1, 186, 160, 120, 7, 143, 243, 72, 227, 210, 143, 20, 92, 145, 51, 179, 193, 180, 88, 232, 140, 21, 147, 189, 79, 166, 251, 194, 86, 183, 8, 232, 193, 2, 17, 0, 0, 0, 3, 216, 28, 38, 192, 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