Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f10d712b58b5bc42aea0753a686e80873b6880fc5d9f9b701249135e9b65419

Tx prefix hash: dd5b4c713a4360b8e8315cc6cc098ea12642ab92dda77711b48d64a26d1071c5
Tx public key: 4051a8dc0de1210ad3501c48bb8f95455d030ce07deeb80b68f513784eb52e98
Timestamp: 1729428380 Timestamp [UCT]: 2024-10-20 12:46:20 Age [y:d:h:m:s]: 01:014:20:33:58
Block: 1135714 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 268979 RingCT/type: yes/0
Extra: 014051a8dc0de1210ad3501c48bb8f95455d030ce07deeb80b68f513784eb52e980211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 706e252cd5ebaf2244ea2fa1c8ddba78ae4c565867f5d64f8c67b5fb72fdb21f 0.600000000000 1619053 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": 1135724, "vin": [ { "gen": { "height": 1135714 } } ], "vout": [ { "amount": 600000000, "target": { "key": "706e252cd5ebaf2244ea2fa1c8ddba78ae4c565867f5d64f8c67b5fb72fdb21f" } } ], "extra": [ 1, 64, 81, 168, 220, 13, 225, 33, 10, 211, 80, 28, 72, 187, 143, 149, 69, 93, 3, 12, 224, 125, 238, 184, 11, 104, 245, 19, 120, 78, 181, 46, 152, 2, 17, 0, 0, 0, 7, 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