Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f219a7357643e9db55a1fed7641cc06e225808ffb275222a84c336c4e15ea6ee

Tx prefix hash: bf798901de5c5daf0ca8a00f45e7c93544b365f59f396f8ea7b910416bea89d4
Tx public key: 013b3bff59352fe22e4cb59b50365f23aa8a853f55306965c9ede0fbd6e493f0
Timestamp: 1721973851 Timestamp [UCT]: 2024-07-26 06:04:11 Age [y:d:h:m:s]: 01:117:02:14:52
Block: 1073913 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 342200 RingCT/type: yes/0
Extra: 01013b3bff59352fe22e4cb59b50365f23aa8a853f55306965c9ede0fbd6e493f0021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 401688f6066cba855bcf229b6bc71c7d5591a6ac9e44906fc5b76256138f6684 0.600000000000 1546422 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": 1073923, "vin": [ { "gen": { "height": 1073913 } } ], "vout": [ { "amount": 600000000, "target": { "key": "401688f6066cba855bcf229b6bc71c7d5591a6ac9e44906fc5b76256138f6684" } } ], "extra": [ 1, 1, 59, 59, 255, 89, 53, 47, 226, 46, 76, 181, 155, 80, 54, 95, 35, 170, 138, 133, 63, 85, 48, 105, 101, 201, 237, 224, 251, 214, 228, 147, 240, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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