Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 033482b3d3c1aeee1c93dd0313baebf25359a9a3bee3975b3c7ec7d444fd60d3

Tx prefix hash: a877ce3962e50103c32b348e114c52de2c7d96f2fc3bce1bade9fcba015348bd
Tx public key: cc6789116db4dee82635baf9e5a3b92907562b8c00091354cd4b1f425f529021
Timestamp: 1702837577 Timestamp [UCT]: 2023-12-17 18:26:17 Age [y:d:h:m:s]: 01:326:12:30:18
Block: 915274 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 492207 RingCT/type: yes/0
Extra: 01cc6789116db4dee82635baf9e5a3b92907562b8c00091354cd4b1f425f52902102110000000233af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 703836db6fefeaa71f5b8ae2b5aab4a54ac9c25676859cd68355d19fb6fe2639 0.600000000000 1372664 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": 915284, "vin": [ { "gen": { "height": 915274 } } ], "vout": [ { "amount": 600000000, "target": { "key": "703836db6fefeaa71f5b8ae2b5aab4a54ac9c25676859cd68355d19fb6fe2639" } } ], "extra": [ 1, 204, 103, 137, 17, 109, 180, 222, 232, 38, 53, 186, 249, 229, 163, 185, 41, 7, 86, 43, 140, 0, 9, 19, 84, 205, 75, 31, 66, 95, 82, 144, 33, 2, 17, 0, 0, 0, 2, 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