Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9668ed68be1cabde590bb62314fef1aa3e48f17bc5dd778e6ef98e0682da2dd0

Tx prefix hash: bd266f086a4d2ac197324c7a1f6a4ec2b0fd198a01202c7f5777ee822c06157a
Tx public key: 471728e8c787f13aed65489655c03e6afe5ab2497a939cb39d4205bf54bea7be
Timestamp: 1735140523 Timestamp [UCT]: 2024-12-25 15:28:43 Age [y:d:h:m:s]: 00:088:11:33:34
Block: 1182958 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 63006 RingCT/type: yes/0
Extra: 01471728e8c787f13aed65489655c03e6afe5ab2497a939cb39d4205bf54bea7be0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a4765c2ca167cda2244a4efccb6ec4dbf205eeb428573f4a1b89e2eb12b954ef 0.600000000000 1669397 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": 1182968, "vin": [ { "gen": { "height": 1182958 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a4765c2ca167cda2244a4efccb6ec4dbf205eeb428573f4a1b89e2eb12b954ef" } } ], "extra": [ 1, 71, 23, 40, 232, 199, 135, 241, 58, 237, 101, 72, 150, 85, 192, 62, 106, 254, 90, 178, 73, 122, 147, 156, 179, 157, 66, 5, 191, 84, 190, 167, 190, 2, 17, 0, 0, 0, 2, 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