Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3866a983d3416384ee4c305e80456504f28afa8d7d3a915ca5a37f83ca3c20b1

Tx prefix hash: 104fc8041e71f741c7faf1e59212fff74ad569de753a5020b5bbddc7f77217d6
Tx public key: 41eea2db3aef9835141552ef4c54b7bf0a1ae627ec6cbc6b375aad76f37a8de9
Timestamp: 1682389020 Timestamp [UCT]: 2023-04-25 02:17:00 Age [y:d:h:m:s]: 01:362:21:37:11
Block: 745986 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 520635 RingCT/type: yes/0
Extra: 0141eea2db3aef9835141552ef4c54b7bf0a1ae627ec6cbc6b375aad76f37a8de9021100000005b3164c24000000000000000000

1 output(s) for total of 2.071280505000 dcy

stealth address amount amount idx
00: aacaf600f5249c65f3f2d6c33e53c68a954f55bf8c8933ba98822a5b4822c59a 2.071280505000 1193489 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": 745996, "vin": [ { "gen": { "height": 745986 } } ], "vout": [ { "amount": 2071280505, "target": { "key": "aacaf600f5249c65f3f2d6c33e53c68a954f55bf8c8933ba98822a5b4822c59a" } } ], "extra": [ 1, 65, 238, 162, 219, 58, 239, 152, 53, 20, 21, 82, 239, 76, 84, 183, 191, 10, 26, 230, 39, 236, 108, 188, 107, 55, 90, 173, 118, 243, 122, 141, 233, 2, 17, 0, 0, 0, 5, 179, 22, 76, 36, 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