Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ac6ee27725d9f6f48f424c71f465378891874d67033ef294f6f9de740bbe269

Tx prefix hash: 991a0e14b28f307ffe627e48c9f465a0d989975ec406c7eda427641ae8ed86ca
Tx public key: f4e66dd47b47ae2fb739689aed71328a0e164ffed98bf6c47ae8206fbe25e8e8
Timestamp: 1713467354 Timestamp [UCT]: 2024-04-18 19:09:14 Age [y:d:h:m:s]: 01:050:12:05:40
Block: 1003383 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 297088 RingCT/type: yes/0
Extra: 01f4e66dd47b47ae2fb739689aed71328a0e164ffed98bf6c47ae8206fbe25e8e802110000001359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cba97845a013a31825b2b36387c10e34bf3329790a1362f047d3f59c2f8a0a52 0.600000000000 1463913 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": 1003393, "vin": [ { "gen": { "height": 1003383 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cba97845a013a31825b2b36387c10e34bf3329790a1362f047d3f59c2f8a0a52" } } ], "extra": [ 1, 244, 230, 109, 212, 123, 71, 174, 47, 183, 57, 104, 154, 237, 113, 50, 138, 14, 22, 79, 254, 217, 139, 246, 196, 122, 232, 32, 111, 190, 37, 232, 232, 2, 17, 0, 0, 0, 19, 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