Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc815df9e37b91e2ed1fe83bcb23d28ad7dac1220418b8653b0462f046cfeaf1

Tx prefix hash: 49e782f281798419784c13a879dc2bdc08f317d1d2ef3e35cfd6dfcdbdd9f92f
Tx public key: 882488e0556f78a91580f0d38993a78944cef5549f480532b5392620e4f3148c
Timestamp: 1698460515 Timestamp [UCT]: 2023-10-28 02:35:15 Age [y:d:h:m:s]: 02:011:23:38:10
Block: 879205 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 528133 RingCT/type: yes/0
Extra: 01882488e0556f78a91580f0d38993a78944cef5549f480532b5392620e4f3148c021100000005faf35c9c000000000000000000

1 output(s) for total of 0.749598784000 dcy

stealth address amount amount idx
00: 7f9c7d43f0e0cca9d227663d27eb4a97b04bcf2a04fd54f524ff229d74e16241 0.749598784000 1334709 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": 879215, "vin": [ { "gen": { "height": 879205 } } ], "vout": [ { "amount": 749598784, "target": { "key": "7f9c7d43f0e0cca9d227663d27eb4a97b04bcf2a04fd54f524ff229d74e16241" } } ], "extra": [ 1, 136, 36, 136, 224, 85, 111, 120, 169, 21, 128, 240, 211, 137, 147, 167, 137, 68, 206, 245, 84, 159, 72, 5, 50, 181, 57, 38, 32, 228, 243, 20, 140, 2, 17, 0, 0, 0, 5, 250, 243, 92, 156, 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