Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 12f9a1ce9b44776594a18e2fbef1bff617076c1187ecf5b7defc1e91a4732b48

Tx prefix hash: fea1f449391031634a962fc7239e42abb7dc109dce41a656a08b9cbc34694fb3
Tx public key: 51c2898262e63ca7e2934fb0a5a9654eeb7a35df03436a85daeb56830c8c2e20
Timestamp: 1710105380 Timestamp [UCT]: 2024-03-10 21:16:20 Age [y:d:h:m:s]: 01:052:20:28:51
Block: 975529 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 298777 RingCT/type: yes/0
Extra: 0151c2898262e63ca7e2934fb0a5a9654eeb7a35df03436a85daeb56830c8c2e200211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dc1625dd5f4cae456ba79d7c7bddbdfd5aea968935c09612243322faa5d323b8 0.600000000000 1435502 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": 975539, "vin": [ { "gen": { "height": 975529 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dc1625dd5f4cae456ba79d7c7bddbdfd5aea968935c09612243322faa5d323b8" } } ], "extra": [ 1, 81, 194, 137, 130, 98, 230, 60, 167, 226, 147, 79, 176, 165, 169, 101, 78, 235, 122, 53, 223, 3, 67, 106, 133, 218, 235, 86, 131, 12, 140, 46, 32, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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