Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb241bb35c7db2bb28f97c5bdc0a7cd2b4fe511ea77cc0ec24c91b0580d65a39

Tx prefix hash: d609eb260199daea1b070553fc38c3b024e2fe663bc4b1727d492674113d6eae
Tx public key: 89d76321ade6854c414db0475b029e8716e5b4e0ddcdc7db24385b946de649ed
Timestamp: 1703804654 Timestamp [UCT]: 2023-12-28 23:04:14 Age [y:d:h:m:s]: 01:116:17:15:44
Block: 923288 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 344535 RingCT/type: yes/0
Extra: 0189d76321ade6854c414db0475b029e8716e5b4e0ddcdc7db24385b946de649ed02110000000c52d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4864e62f499e86d6b7ca0fc6cca5f1b6a56d685951b96cb65e9c519fb77c6d63 0.600000000000 1381016 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": 923298, "vin": [ { "gen": { "height": 923288 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4864e62f499e86d6b7ca0fc6cca5f1b6a56d685951b96cb65e9c519fb77c6d63" } } ], "extra": [ 1, 137, 215, 99, 33, 173, 230, 133, 76, 65, 77, 176, 71, 91, 2, 158, 135, 22, 229, 180, 224, 221, 205, 199, 219, 36, 56, 91, 148, 109, 230, 73, 237, 2, 17, 0, 0, 0, 12, 82, 212, 126, 148, 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