Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7834a00297c6dd4691b8346282eb9e49ac0a7c74db74ec8ce0561ff69ff6dd27

Tx prefix hash: 4b04273927badde4d7734fcdc7deb8eb5532f53511385b95fc0b00e01207d2c5
Tx public key: 9c8a63d96f9fcfd726e5f06ecfa5f0570b37eb17295f0c56d4053ddab553fa63
Timestamp: 1700962961 Timestamp [UCT]: 2023-11-26 01:42:41 Age [y:d:h:m:s]: 01:090:14:59:34
Block: 899725 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 325898 RingCT/type: yes/0
Extra: 019c8a63d96f9fcfd726e5f06ecfa5f0570b37eb17295f0c56d4053ddab553fa6302110000000175e3f0e9000000000000000000

1 output(s) for total of 0.640969796000 dcy

stealth address amount amount idx
00: 5dedcea6fc918a8c442bab98955aebbd2ec1b5aea2c907e531d42269b60242fd 0.640969796000 1356188 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": 899735, "vin": [ { "gen": { "height": 899725 } } ], "vout": [ { "amount": 640969796, "target": { "key": "5dedcea6fc918a8c442bab98955aebbd2ec1b5aea2c907e531d42269b60242fd" } } ], "extra": [ 1, 156, 138, 99, 217, 111, 159, 207, 215, 38, 229, 240, 110, 207, 165, 240, 87, 11, 55, 235, 23, 41, 95, 12, 86, 212, 5, 61, 218, 181, 83, 250, 99, 2, 17, 0, 0, 0, 1, 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