Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 17832514d239e5a92b34ade97929e78fd6d81bfa079f7e783c0c63666e904e40

Tx prefix hash: f4e77530f1b07aca409b62abaa108ad60dd7077deacd0d69b0bca25fc388e7f7
Tx public key: 777b12d46dca24cd05dd18dfbaa515d7f2269da9cbe148dc00345c62f97f3213
Timestamp: 1702905450 Timestamp [UCT]: 2023-12-18 13:17:30 Age [y:d:h:m:s]: 01:145:14:18:30
Block: 915833 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 365207 RingCT/type: yes/0
Extra: 01777b12d46dca24cd05dd18dfbaa515d7f2269da9cbe148dc00345c62f97f321302110000000475e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b5b3fcedd69910403d5f2e7fd070e91c0347e1d9cf1388cf23ea6aadfa2f507 0.600000000000 1373267 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": 915843, "vin": [ { "gen": { "height": 915833 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b5b3fcedd69910403d5f2e7fd070e91c0347e1d9cf1388cf23ea6aadfa2f507" } } ], "extra": [ 1, 119, 123, 18, 212, 109, 202, 36, 205, 5, 221, 24, 223, 186, 165, 21, 215, 242, 38, 157, 169, 203, 225, 72, 220, 0, 52, 92, 98, 249, 127, 50, 19, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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