Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0cd363513cd00ad2f288155f22bef175ce522c55bb4c64f025eda1af61c34709

Tx prefix hash: f5d9d0d068964637f03b99050820d355305d5894217200c6003dd06ab5a86922
Tx public key: 3038d9b5b4f2c01ae2e5bf07dcc3ea4bd6bb78632d7a83832b1ce113b1c96588
Timestamp: 1656869896 Timestamp [UCT]: 2022-07-03 17:38:16 Age [y:d:h:m:s]: 02:187:11:47:27
Block: 535892 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 655361 RingCT/type: yes/0
Extra: 013038d9b5b4f2c01ae2e5bf07dcc3ea4bd6bb78632d7a83832b1ce113b1c9658802110000000275e3f0e9000000000000000000

1 output(s) for total of 10.288865680000 dcy

stealth address amount amount idx
00: f1b2284ff9da76e3311aefda5225f88ce6578c9264f43a8f27121f0f3e3769ea 10.288865680000 965561 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": 535902, "vin": [ { "gen": { "height": 535892 } } ], "vout": [ { "amount": 10288865680, "target": { "key": "f1b2284ff9da76e3311aefda5225f88ce6578c9264f43a8f27121f0f3e3769ea" } } ], "extra": [ 1, 48, 56, 217, 181, 180, 242, 192, 26, 226, 229, 191, 7, 220, 195, 234, 75, 214, 187, 120, 99, 45, 122, 131, 131, 43, 28, 225, 19, 177, 201, 101, 136, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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