Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f963dd6b8dd350f78cc9185211106ec7ab18c125951a249ec6e29c0f85eadce7

Tx prefix hash: bb7484475a8a0f8c96ab6685bc05057142cf092b165d76cb01a84a13b1e7350a
Tx public key: d3d7bf97711214c2e09b4dcd78e572b6d3682b9a7f5f4287686432fa04168691
Timestamp: 1575857093 Timestamp [UCT]: 2019-12-09 02:04:53 Age [y:d:h:m:s]: 05:152:06:45:29
Block: 23506 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1254831 RingCT/type: yes/0
Extra: 01d3d7bf97711214c2e09b4dcd78e572b6d3682b9a7f5f4287686432fa041686910211000000029159db1e000000000000000000

1 output(s) for total of 512.998075648000 dcy

stealth address amount amount idx
00: 28a7cb9ff048b223feefe774c72c41b0e9baa71ee23c001ee0e90210e3a5aec5 512.998075648000 37905 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": 23516, "vin": [ { "gen": { "height": 23506 } } ], "vout": [ { "amount": 512998075648, "target": { "key": "28a7cb9ff048b223feefe774c72c41b0e9baa71ee23c001ee0e90210e3a5aec5" } } ], "extra": [ 1, 211, 215, 191, 151, 113, 18, 20, 194, 224, 155, 77, 205, 120, 229, 114, 182, 211, 104, 43, 154, 127, 95, 66, 135, 104, 100, 50, 250, 4, 22, 134, 145, 2, 17, 0, 0, 0, 2, 145, 89, 219, 30, 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