Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08b77a3c6c0dc1282b5d41bf1a18415d79e360a7af74c76935ba412d5d3cd031

Tx prefix hash: 093e7d6a861beee43b9815f6f5ac1b0b4c946122e0f7257517d3402431169ace
Tx public key: 50e321e87ae3b022ef5e94392635c6daa167ccf47d18198353a8623633338a33
Timestamp: 1617634767 Timestamp [UCT]: 2021-04-05 14:59:27 Age [y:d:h:m:s]: 04:040:20:08:17
Block: 233790 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1049629 RingCT/type: yes/0
Extra: 0150e321e87ae3b022ef5e94392635c6daa167ccf47d18198353a8623633338a33021100000040f18a1c63000000000000000000

1 output(s) for total of 103.123407561000 dcy

stealth address amount amount idx
00: c5569414333bbcb9df034902e6ee3c051b38eeba7dffcea361d2efdbb4e0b4b2 103.123407561000 485424 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": 233800, "vin": [ { "gen": { "height": 233790 } } ], "vout": [ { "amount": 103123407561, "target": { "key": "c5569414333bbcb9df034902e6ee3c051b38eeba7dffcea361d2efdbb4e0b4b2" } } ], "extra": [ 1, 80, 227, 33, 232, 122, 227, 176, 34, 239, 94, 148, 57, 38, 53, 198, 218, 161, 103, 204, 244, 125, 24, 25, 131, 83, 168, 98, 54, 51, 51, 138, 51, 2, 17, 0, 0, 0, 64, 241, 138, 28, 99, 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