Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2ee2c4adafc82596a8ee07c2a1a977634234cb5f42fa02b67f454d4307e1265

Tx prefix hash: 65863e7a2e0135d86b905ccda16daea7249713a750c21d11031a8b0ed756c050
Tx public key: a776860708d94d4e376b382fbad252b27c3b917f0ea91f89677ba96a6f58da9d
Timestamp: 1719740702 Timestamp [UCT]: 2024-06-30 09:45:02 Age [y:d:h:m:s]: 01:132:04:54:17
Block: 1055403 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 353018 RingCT/type: yes/0
Extra: 01a776860708d94d4e376b382fbad252b27c3b917f0ea91f89677ba96a6f58da9d0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c166f76616e99b49fa663eb5f560441b420ccf1a30eaedeca9551e729295314e 0.600000000000 1525802 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": 1055413, "vin": [ { "gen": { "height": 1055403 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c166f76616e99b49fa663eb5f560441b420ccf1a30eaedeca9551e729295314e" } } ], "extra": [ 1, 167, 118, 134, 7, 8, 217, 77, 78, 55, 107, 56, 47, 186, 210, 82, 178, 124, 59, 145, 127, 14, 169, 31, 137, 103, 123, 169, 106, 111, 88, 218, 157, 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