Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00dc8fac2bfd62911af22574a7ee6261f1677a56b80c894f3b91ecfdbe5a9c27

Tx prefix hash: bc28dc2acae536e520798e990f8f09c6be4a06a8a09a4e066959e36e76d9d0c5
Tx public key: c91b3d12a7e782c7e929a1e64214fae2b7597172eaad12d3cc996cdb52bb310e
Timestamp: 1694850578 Timestamp [UCT]: 2023-09-16 07:49:38 Age [y:d:h:m:s]: 00:290:17:33:00
Block: 849245 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 208050 RingCT/type: yes/0
Extra: 01c91b3d12a7e782c7e929a1e64214fae2b7597172eaad12d3cc996cdb52bb310e02110000000a4b8f5122000000000000000000

1 output(s) for total of 0.942103971000 dcy

stealth address amount amount idx
00: d0d2cbb69721a68b7807bf63b1b9aa25c4be751c865ca5ac0b51723e2c352e6d 0.942103971000 1302895 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": 849255, "vin": [ { "gen": { "height": 849245 } } ], "vout": [ { "amount": 942103971, "target": { "key": "d0d2cbb69721a68b7807bf63b1b9aa25c4be751c865ca5ac0b51723e2c352e6d" } } ], "extra": [ 1, 201, 27, 61, 18, 167, 231, 130, 199, 233, 41, 161, 230, 66, 20, 250, 226, 183, 89, 113, 114, 234, 173, 18, 211, 204, 153, 108, 219, 82, 187, 49, 14, 2, 17, 0, 0, 0, 10, 75, 143, 81, 34, 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