Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f65d817fe5a6ac98ae4fe6c8bf13ce04cd8786beb4300d426204c4c97b2fa1c9

Tx prefix hash: 74e574a8e2726463ab4949587c0592afbb00c777cba8a3a0dd9ba2043fc19f23
Tx public key: 67064523c9f6dfe4e84c3b552d081e6030efc4f054ccc4fa00832482978c5453
Timestamp: 1677070222 Timestamp [UCT]: 2023-02-22 12:50:22 Age [y:d:h:m:s]: 02:063:19:53:19
Block: 702530 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 567224 RingCT/type: yes/0
Extra: 0167064523c9f6dfe4e84c3b552d081e6030efc4f054ccc4fa00832482978c545302110000000133af99f4000000000000000000

1 output(s) for total of 2.885535260000 dcy

stealth address amount amount idx
00: 407518151040400f5efc4bedaa7b4c4a1a897e3e82531f4f736f4f41229adf41 2.885535260000 1146045 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": 702540, "vin": [ { "gen": { "height": 702530 } } ], "vout": [ { "amount": 2885535260, "target": { "key": "407518151040400f5efc4bedaa7b4c4a1a897e3e82531f4f736f4f41229adf41" } } ], "extra": [ 1, 103, 6, 69, 35, 201, 246, 223, 228, 232, 76, 59, 85, 45, 8, 30, 96, 48, 239, 196, 240, 84, 204, 196, 250, 0, 131, 36, 130, 151, 140, 84, 83, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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