Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a98cc70bb6c42342c1f71da245c943dda9e5b82b3ed090e1bcd615bcb67d350

Tx prefix hash: 719c0cd0cf54d009f1bce5574a027e46879fdf2f690f15b758fe81e6223caa35
Tx public key: 952f4f2f33b0d00761e33670bab2d26fbb667c10a92562a5240fa203cc56d1dc
Timestamp: 1705932328 Timestamp [UCT]: 2024-01-22 14:05:28 Age [y:d:h:m:s]: 01:291:20:06:00
Block: 940890 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 467407 RingCT/type: yes/0
Extra: 01952f4f2f33b0d00761e33670bab2d26fbb667c10a92562a5240fa203cc56d1dc02110000000b59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 441cc92b290d3856c996694fd029fc2fafe378f347c8638f4b1a22695ce8f0e1 0.600000000000 1399030 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": 940900, "vin": [ { "gen": { "height": 940890 } } ], "vout": [ { "amount": 600000000, "target": { "key": "441cc92b290d3856c996694fd029fc2fafe378f347c8638f4b1a22695ce8f0e1" } } ], "extra": [ 1, 149, 47, 79, 47, 51, 176, 208, 7, 97, 227, 54, 112, 186, 178, 210, 111, 187, 102, 124, 16, 169, 37, 98, 165, 36, 15, 162, 3, 204, 86, 209, 220, 2, 17, 0, 0, 0, 11, 89, 218, 211, 245, 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