Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 42d355fc62221175dd1fcb64011a696bdfc395aa553667e10803907b37e33e54

Tx prefix hash: d7ac7b63c625d6b0464ab513aa173d75d2bca8c1bda558e3d4d3eb54071ab2bc
Tx public key: 087aaf9c7f933668b25e09f2d70a2f442aae70eec8aa4d43f9968e10fd377d1d
Timestamp: 1709034164 Timestamp [UCT]: 2024-02-27 11:42:44 Age [y:d:h:m:s]: 01:258:00:52:48
Block: 966648 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 443151 RingCT/type: yes/0
Extra: 01087aaf9c7f933668b25e09f2d70a2f442aae70eec8aa4d43f9968e10fd377d1d0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3e1df7b18defd54683b8d8842e89ecff6cff2fab0f3decf9bfc9c80cb5125b45 0.600000000000 1426415 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": 966658, "vin": [ { "gen": { "height": 966648 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3e1df7b18defd54683b8d8842e89ecff6cff2fab0f3decf9bfc9c80cb5125b45" } } ], "extra": [ 1, 8, 122, 175, 156, 127, 147, 54, 104, 178, 94, 9, 242, 215, 10, 47, 68, 42, 174, 112, 238, 200, 170, 77, 67, 249, 150, 142, 16, 253, 55, 125, 29, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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