Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f71e0d3a6efbc7a669e1bd1e322ddef8ce0565af2e811bb46c338e470d76a5ca

Tx prefix hash: 6dfa10890690218d6e621c27194b7fac142ad1444a577a74c3d7c6d0c1684afd
Tx public key: 610d9449e04bb6f402852fc58bd5ed349234c02fae4aea97939e0808c3c14091
Timestamp: 1714251777 Timestamp [UCT]: 2024-04-27 21:02:57 Age [y:d:h:m:s]: 01:243:16:35:39
Block: 1009896 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 432864 RingCT/type: yes/0
Extra: 01610d9449e04bb6f402852fc58bd5ed349234c02fae4aea97939e0808c3c1409102110000000b7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4bc1613a3119366bb1624877c02f6a70ed5ac6ae04b91c52e398a7f392bdbf5d 0.600000000000 1471698 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": 1009906, "vin": [ { "gen": { "height": 1009896 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4bc1613a3119366bb1624877c02f6a70ed5ac6ae04b91c52e398a7f392bdbf5d" } } ], "extra": [ 1, 97, 13, 148, 73, 224, 75, 182, 244, 2, 133, 47, 197, 139, 213, 237, 52, 146, 52, 192, 47, 174, 74, 234, 151, 147, 158, 8, 8, 195, 193, 64, 145, 2, 17, 0, 0, 0, 11, 122, 156, 244, 199, 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