Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08fda739c80e97267f8e3c20deb82e0df3c68e3d9aa4f9f8fcda74fbbdc9f321

Tx prefix hash: aa4012a11beb03f58133bc0a8038e52fa0e915943410647cd3b0dc6d5aa79222
Tx public key: 7610950786d9b4ad9562573c9961bb41d2215328ddb2de326d4033c15d3450a2
Timestamp: 1734644134 Timestamp [UCT]: 2024-12-19 21:35:34 Age [y:d:h:m:s]: 00:103:04:45:27
Block: 1178869 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73510 RingCT/type: yes/0
Extra: 017610950786d9b4ad9562573c9961bb41d2215328ddb2de326d4033c15d3450a20211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 308beb968be3ca7336f17bf8dc8d303a68f83d5fb11d24b2de953f656208f309 0.600000000000 1665258 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": 1178879, "vin": [ { "gen": { "height": 1178869 } } ], "vout": [ { "amount": 600000000, "target": { "key": "308beb968be3ca7336f17bf8dc8d303a68f83d5fb11d24b2de953f656208f309" } } ], "extra": [ 1, 118, 16, 149, 7, 134, 217, 180, 173, 149, 98, 87, 60, 153, 97, 187, 65, 210, 33, 83, 40, 221, 178, 222, 50, 109, 64, 51, 193, 93, 52, 80, 162, 2, 17, 0, 0, 0, 5, 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