Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f447535be4f3e4444d19b057ca65b9f0312e3f1bb8f3915cce8a338ae722d995

Tx prefix hash: 7f7ee0238984cf45ddc055f4dee9a90a995800279669772e5e57bc36fd7fd34d
Tx public key: 0c7430fa488c10aa927c0cecdf9fd37138763bce78448341aeff36b525e6e00b
Timestamp: 1693965159 Timestamp [UCT]: 2023-09-06 01:52:39 Age [y:d:h:m:s]: 01:213:08:55:38
Block: 841894 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 413612 RingCT/type: yes/0
Extra: 010c7430fa488c10aa927c0cecdf9fd37138763bce78448341aeff36b525e6e00b02110000000675e3f0e9000000000000000000

1 output(s) for total of 0.996450569000 dcy

stealth address amount amount idx
00: d6098de0fb906cbd908bec6120f553021e9e9dc9e3eb37e58cafe9e38a26ba1d 0.996450569000 1294968 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": 841904, "vin": [ { "gen": { "height": 841894 } } ], "vout": [ { "amount": 996450569, "target": { "key": "d6098de0fb906cbd908bec6120f553021e9e9dc9e3eb37e58cafe9e38a26ba1d" } } ], "extra": [ 1, 12, 116, 48, 250, 72, 140, 16, 170, 146, 124, 12, 236, 223, 159, 211, 113, 56, 118, 59, 206, 120, 68, 131, 65, 174, 255, 54, 181, 37, 230, 224, 11, 2, 17, 0, 0, 0, 6, 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