Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c0a3aef85f577ce7b0e5e03f8f363bdcc4ef9d8818b8d6b6cf307a7eb527ff0

Tx prefix hash: c92429bd3a12c834919d8cb98c2166c550eda858e7d26758c7888e7a4db4113d
Tx public key: e60648d7d236869fd69c0bd8253af7c76216ba3a0c9a3fc7f2251ed30b0edc29
Timestamp: 1705629015 Timestamp [UCT]: 2024-01-19 01:50:15 Age [y:d:h:m:s]: 01:098:08:23:20
Block: 938394 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 331405 RingCT/type: yes/0
Extra: 01e60648d7d236869fd69c0bd8253af7c76216ba3a0c9a3fc7f2251ed30b0edc290211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fecb7a6dcfe9e3d045aabd25c5d97f0e9f3f41ce18a13a4b0a5aaa0f96610676 0.600000000000 1396464 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": 938404, "vin": [ { "gen": { "height": 938394 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fecb7a6dcfe9e3d045aabd25c5d97f0e9f3f41ce18a13a4b0a5aaa0f96610676" } } ], "extra": [ 1, 230, 6, 72, 215, 210, 54, 134, 159, 214, 156, 11, 216, 37, 58, 247, 199, 98, 22, 186, 58, 12, 154, 63, 199, 242, 37, 30, 211, 11, 14, 220, 41, 2, 17, 0, 0, 0, 5, 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