Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ace4f1f1264b2fb75c39c549da5348631a16ac9f86c034c1830c9c0ed6ecfe35

Tx prefix hash: 8a0fc738ee7cf6a882a56a11df7852142333481a677a0bf9637b86661dd2e317
Tx public key: c579272c098cb093ad54ac34be254a413c267354b4d7cd0de295c833e14d23d8
Timestamp: 1693501938 Timestamp [UCT]: 2023-08-31 17:12:18 Age [y:d:h:m:s]: 02:095:12:10:25
Block: 838050 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 588001 RingCT/type: yes/0
Extra: 01c579272c098cb093ad54ac34be254a413c267354b4d7cd0de295c833e14d23d802110000000927f2911c000000000000000000

1 output(s) for total of 1.026106723000 dcy

stealth address amount amount idx
00: 05f6c507fecfa338badfbbd192322fbfb508c32b6f1a8e8643d24340ac25c386 1.026106723000 1290748 of 0

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": 838060, "vin": [ { "gen": { "height": 838050 } } ], "vout": [ { "amount": 1026106723, "target": { "key": "05f6c507fecfa338badfbbd192322fbfb508c32b6f1a8e8643d24340ac25c386" } } ], "extra": [ 1, 197, 121, 39, 44, 9, 140, 176, 147, 173, 84, 172, 52, 190, 37, 74, 65, 60, 38, 115, 84, 180, 215, 205, 13, 226, 149, 200, 51, 225, 77, 35, 216, 2, 17, 0, 0, 0, 9, 39, 242, 145, 28, 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