Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be04566e97e78957444ba4e786569d7fbeaf67e58c43733bcf815d0b2a1e1ff5

Tx prefix hash: d3aec1f8d5b9a6bdd2faa8fbc90e7db466e630ac5e674d5bdbd650fd7f8aaee6
Tx public key: 01ccf10fb918ff0098d5ad7114915b149608c32953e70ee42794d5c652c089a0
Timestamp: 1694843068 Timestamp [UCT]: 2023-09-16 05:44:28 Age [y:d:h:m:s]: 01:205:22:34:05
Block: 849180 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 408271 RingCT/type: yes/0
Extra: 0101ccf10fb918ff0098d5ad7114915b149608c32953e70ee42794d5c652c089a00211000000034b8f5122000000000000000000

1 output(s) for total of 0.942571288000 dcy

stealth address amount amount idx
00: 2c632743c6ef91a87e0712a95460795d3ab458730162bf047b5b914a57572db4 0.942571288000 1302826 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": 849190, "vin": [ { "gen": { "height": 849180 } } ], "vout": [ { "amount": 942571288, "target": { "key": "2c632743c6ef91a87e0712a95460795d3ab458730162bf047b5b914a57572db4" } } ], "extra": [ 1, 1, 204, 241, 15, 185, 24, 255, 0, 152, 213, 173, 113, 20, 145, 91, 20, 150, 8, 195, 41, 83, 231, 14, 228, 39, 148, 213, 198, 82, 192, 137, 160, 2, 17, 0, 0, 0, 3, 75, 143, 81, 34, 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