Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a6870e14a0ce3ab009c2e55b3c9f1d5f70d25eec6ffb2868344b4adf9c8ff49

Tx prefix hash: c60269e657d1fb2a8f473fd08848f3f5afedb7b599d47abe266073fe71548af4
Tx public key: cd271cde88bdc1fcf369f3d264342f911c301e824014e639bd3cbc2ef31c73ce
Timestamp: 1712806039 Timestamp [UCT]: 2024-04-11 03:27:19 Age [y:d:h:m:s]: 00:272:13:03:50
Block: 997889 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 195107 RingCT/type: yes/0
Extra: 01cd271cde88bdc1fcf369f3d264342f911c301e824014e639bd3cbc2ef31c73ce02110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd82bcd4910be93a4b4a7235de689b2aaa157ca096c4b5fe5c4f9aa8e69d168e 0.600000000000 1458323 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": 997899, "vin": [ { "gen": { "height": 997889 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd82bcd4910be93a4b4a7235de689b2aaa157ca096c4b5fe5c4f9aa8e69d168e" } } ], "extra": [ 1, 205, 39, 28, 222, 136, 189, 193, 252, 243, 105, 243, 210, 100, 52, 47, 145, 28, 48, 30, 130, 64, 20, 230, 57, 189, 60, 188, 46, 243, 28, 115, 206, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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