Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7761965a8f9ee67295dcf7c356dc37d2c105332770c6b42d6ae77c91f9e796e3

Tx prefix hash: c7687b43c3e8f55e474a736a770afeee710d18909957a7fe3e392d0e6a1bd83a
Tx public key: d3b9c3d8a156070fb2abd8e8683f5a56082c19108cf3748286132accdd691c89
Timestamp: 1734299523 Timestamp [UCT]: 2024-12-15 21:52:03 Age [y:d:h:m:s]: 00:185:02:35:54
Block: 1176015 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 131993 RingCT/type: yes/0
Extra: 01d3b9c3d8a156070fb2abd8e8683f5a56082c19108cf3748286132accdd691c890211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a0cf40bb2c16a8c316f2fffefb88103e3f73b93cd102b4897e322e9196320119 0.600000000000 1662342 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": 1176025, "vin": [ { "gen": { "height": 1176015 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0cf40bb2c16a8c316f2fffefb88103e3f73b93cd102b4897e322e9196320119" } } ], "extra": [ 1, 211, 185, 195, 216, 161, 86, 7, 15, 178, 171, 216, 232, 104, 63, 90, 86, 8, 44, 25, 16, 140, 243, 116, 130, 134, 19, 42, 204, 221, 105, 28, 137, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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