Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 068154404dcb3dfbbf7e12072bbf7d336c2a16cb22cc91e5118860ce3af64a8c

Tx prefix hash: 7bbee871ff53cfb98b047ee6a9bee50651285738ae9b55fd3339d7c870b9e949
Tx public key: dccdab8c0e85f3cdd13eddc7ba527a286d1703e83b270537b44393ea7e7ce286
Timestamp: 1703796544 Timestamp [UCT]: 2023-12-28 20:49:04 Age [y:d:h:m:s]: 01:315:03:16:16
Block: 923221 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 484060 RingCT/type: yes/0
Extra: 01dccdab8c0e85f3cdd13eddc7ba527a286d1703e83b270537b44393ea7e7ce286021100000003ad5694ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 88dba080ed617d44f41225bb0dfe8f72245e210cb7fe556a2aebcf04dc2fd3d3 0.600000000000 1380947 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": 923231, "vin": [ { "gen": { "height": 923221 } } ], "vout": [ { "amount": 600000000, "target": { "key": "88dba080ed617d44f41225bb0dfe8f72245e210cb7fe556a2aebcf04dc2fd3d3" } } ], "extra": [ 1, 220, 205, 171, 140, 14, 133, 243, 205, 209, 62, 221, 199, 186, 82, 122, 40, 109, 23, 3, 232, 59, 39, 5, 55, 180, 67, 147, 234, 126, 124, 226, 134, 2, 17, 0, 0, 0, 3, 173, 86, 148, 172, 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