Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 335db22fe6fcfe4288a507cef33b7b9f9b56dacd601570af252b0f660b1f75f2

Tx prefix hash: 3005c2f1e845266fd330f595a363d6a3bddff637803aec8771d168c36bd6e20e
Tx public key: b2fefcc0f8b9b8e6db404f6312791a5f1e20646280ffd4e766c07acdbe19c810
Timestamp: 1590522987 Timestamp [UCT]: 2020-05-26 19:56:27 Age [y:d:h:m:s]: 04:215:01:35:09
Block: 103688 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1080160 RingCT/type: yes/0
Extra: 01b2fefcc0f8b9b8e6db404f6312791a5f1e20646280ffd4e766c07acdbe19c8100211000000088a2ee0d9000000000000000000

1 output(s) for total of 278.262309229000 dcy

stealth address amount amount idx
00: 312ce29ef7d848ec9a1d7b94c237e0cbc4d172b0fb781f1da34761ea462c142a 278.262309229000 181793 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": 103698, "vin": [ { "gen": { "height": 103688 } } ], "vout": [ { "amount": 278262309229, "target": { "key": "312ce29ef7d848ec9a1d7b94c237e0cbc4d172b0fb781f1da34761ea462c142a" } } ], "extra": [ 1, 178, 254, 252, 192, 248, 185, 184, 230, 219, 64, 79, 99, 18, 121, 26, 95, 30, 32, 100, 98, 128, 255, 212, 231, 102, 192, 122, 205, 190, 25, 200, 16, 2, 17, 0, 0, 0, 8, 138, 46, 224, 217, 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