Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 669b8b7e7a199129686baa9d943ae6a1ced5e45326dca02f2c49c9184e436f08

Tx prefix hash: f58b4690aa3342e49e80795292961a297768ff109f5a4c03f993f71f2b593d46
Tx public key: 16028295e9deffe5cdbee29f4f28594eb50df4c52480e97b702903ccd081bd7b
Timestamp: 1715297408 Timestamp [UCT]: 2024-05-09 23:30:08 Age [y:d:h:m:s]: 01:033:14:40:53
Block: 1018565 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 284937 RingCT/type: yes/0
Extra: 0116028295e9deffe5cdbee29f4f28594eb50df4c52480e97b702903ccd081bd7b02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 87aa5ae873c0c79a9b2d872a564c852a8290824aacdb18e2da5fb02b87f86978 0.600000000000 1482358 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": 1018575, "vin": [ { "gen": { "height": 1018565 } } ], "vout": [ { "amount": 600000000, "target": { "key": "87aa5ae873c0c79a9b2d872a564c852a8290824aacdb18e2da5fb02b87f86978" } } ], "extra": [ 1, 22, 2, 130, 149, 233, 222, 255, 229, 205, 190, 226, 159, 79, 40, 89, 78, 181, 13, 244, 197, 36, 128, 233, 123, 112, 41, 3, 204, 208, 129, 189, 123, 2, 17, 0, 0, 0, 1, 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