Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a43549b02f2af56d10567bd11f4d21bb152701361556e39865545ee75df88c03

Tx prefix hash: fb7e172f34f43ab87b31449fe9756995638a1323b8bcf4ea4cec715bc69e451e
Tx public key: 1f992217c352c8d753e55dcac2e9ecda35295c39d09fa1f46f2eef3386ca92e6
Timestamp: 1712199906 Timestamp [UCT]: 2024-04-04 03:05:06 Age [y:d:h:m:s]: 01:002:20:38:38
Block: 992855 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 263021 RingCT/type: yes/0
Extra: 011f992217c352c8d753e55dcac2e9ecda35295c39d09fa1f46f2eef3386ca92e60211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d83c18f6291e8c30f7300f1999acbba3ee8c435b9ec60eac6d6e99cd1cf7c928 0.600000000000 1453231 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": 992865, "vin": [ { "gen": { "height": 992855 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d83c18f6291e8c30f7300f1999acbba3ee8c435b9ec60eac6d6e99cd1cf7c928" } } ], "extra": [ 1, 31, 153, 34, 23, 195, 82, 200, 215, 83, 229, 93, 202, 194, 233, 236, 218, 53, 41, 92, 57, 208, 159, 161, 244, 111, 46, 239, 51, 134, 202, 146, 230, 2, 17, 0, 0, 0, 3, 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