Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c796d896c9ad5cb45145d97d6b86ac2b4427283b81d6b80b58307ec0d8f314a

Tx prefix hash: bca9cb6914b2d126ee1bcf381783687067574a48fcf9c43e59d30215834e1a73
Tx public key: a29da01e69faa71e956c66aadccdc2d6304a3ff03063f1fe53f970df90856711
Timestamp: 1682335922 Timestamp [UCT]: 2023-04-24 11:32:02 Age [y:d:h:m:s]: 01:223:04:52:04
Block: 745550 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 420977 RingCT/type: yes/0
Extra: 01a29da01e69faa71e956c66aadccdc2d6304a3ff03063f1fe53f970df9085671102110000000733af99f4000000000000000000

1 output(s) for total of 2.078181944000 dcy

stealth address amount amount idx
00: 0e826c62b2e3444a5ce65ed2488256a8b72e071c0c998e0d8da5c35bf801fba3 2.078181944000 1193009 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": 745560, "vin": [ { "gen": { "height": 745550 } } ], "vout": [ { "amount": 2078181944, "target": { "key": "0e826c62b2e3444a5ce65ed2488256a8b72e071c0c998e0d8da5c35bf801fba3" } } ], "extra": [ 1, 162, 157, 160, 30, 105, 250, 167, 30, 149, 108, 102, 170, 220, 205, 194, 214, 48, 74, 63, 240, 48, 99, 241, 254, 83, 249, 112, 223, 144, 133, 103, 17, 2, 17, 0, 0, 0, 7, 51, 175, 153, 244, 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