Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9b5a4ba751b5e059f84dc119b7b0f6cad015835d59cd0a3a03daa408f1df9e2b

Tx prefix hash: 3aba080cd4fcf16c9b1cf96f917ed49a7b9b068d740428ea2fa21cf2554d1305
Tx public key: 140341dbe39481cb7f447b37c0fd5fd8dd332628fbd049fd9569c83593eda96d
Timestamp: 1624995602 Timestamp [UCT]: 2021-06-29 19:40:02 Age [y:d:h:m:s]: 03:131:23:33:31
Block: 285443 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 863279 RingCT/type: yes/0
Extra: 01140341dbe39481cb7f447b37c0fd5fd8dd332628fbd049fd9569c83593eda96d0211000000163525d189000000000000000000

1 output(s) for total of 69.537144739000 dcy

stealth address amount amount idx
00: b697f607d6ae5c0505ca65b97b53353361e6e667317e01130e49f9c4f7cbdc96 69.537144739000 597642 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": 285453, "vin": [ { "gen": { "height": 285443 } } ], "vout": [ { "amount": 69537144739, "target": { "key": "b697f607d6ae5c0505ca65b97b53353361e6e667317e01130e49f9c4f7cbdc96" } } ], "extra": [ 1, 20, 3, 65, 219, 227, 148, 129, 203, 127, 68, 123, 55, 192, 253, 95, 216, 221, 51, 38, 40, 251, 208, 73, 253, 149, 105, 200, 53, 147, 237, 169, 109, 2, 17, 0, 0, 0, 22, 53, 37, 209, 137, 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