Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff46fe97ef730c3f2af1f4a5be7ec0b95d0d55c191f9f00a73104ebc61b155de

Tx prefix hash: 16a8c05ff339a7e1fcbdf83438950e062dbde368efa1fd3a57510bc7f46c3aa5
Tx public key: 1732f84c92e53e1df6c24b9d3f35d08dfffd9afe371b7f0b0c09b8cf07303bba
Timestamp: 1707089140 Timestamp [UCT]: 2024-02-04 23:25:40 Age [y:d:h:m:s]: 01:063:23:39:20
Block: 950504 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 306787 RingCT/type: yes/0
Extra: 011732f84c92e53e1df6c24b9d3f35d08dfffd9afe371b7f0b0c09b8cf07303bba0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5ee3661bec3907ac8f1df8df81fc14e506a03d9402b9fbe51edc338397eb3186 0.600000000000 1409136 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": 950514, "vin": [ { "gen": { "height": 950504 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5ee3661bec3907ac8f1df8df81fc14e506a03d9402b9fbe51edc338397eb3186" } } ], "extra": [ 1, 23, 50, 248, 76, 146, 229, 62, 29, 246, 194, 75, 157, 63, 53, 208, 141, 255, 253, 154, 254, 55, 27, 127, 11, 12, 9, 184, 207, 7, 48, 59, 186, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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