Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 44a032300c5fc0a9cb691d91d5fde339e729a184596933b9b2ae25b725441b00

Tx prefix hash: 958e1e178ae7daaa93649e566bf41b07820d126a0161bf59b23050e7eea35775
Tx public key: cf08bd0dcae7cdccaa2e263c4893e7f87b8a2c99a6ec995d756be7edf13d2407
Timestamp: 1727023994 Timestamp [UCT]: 2024-09-22 16:53:14 Age [y:d:h:m:s]: 00:172:23:05:46
Block: 1115794 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 123436 RingCT/type: yes/0
Extra: 01cf08bd0dcae7cdccaa2e263c4893e7f87b8a2c99a6ec995d756be7edf13d240702110000000c91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: adcfec57fccadb79ce2c0abf8a132d24ef7799b9fd3b98106812e10928e9d8e0 0.600000000000 1596047 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": 1115804, "vin": [ { "gen": { "height": 1115794 } } ], "vout": [ { "amount": 600000000, "target": { "key": "adcfec57fccadb79ce2c0abf8a132d24ef7799b9fd3b98106812e10928e9d8e0" } } ], "extra": [ 1, 207, 8, 189, 13, 202, 231, 205, 204, 170, 46, 38, 60, 72, 147, 231, 248, 123, 138, 44, 153, 166, 236, 153, 93, 117, 107, 231, 237, 241, 61, 36, 7, 2, 17, 0, 0, 0, 12, 145, 225, 60, 4, 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