Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d7124a0333455264bb8accc1d399b618a758f2842e4e9aa54c828644b721d54d

Tx prefix hash: a93973678f1ac4cb7adfcc672673ebbb17965f902faf6aee5169d9bdf32f7d90
Tx public key: 88301f2b121d640c4c8b9e201b885639076995850b405e3578d3d2c95569cbfd
Timestamp: 1578726494 Timestamp [UCT]: 2020-01-11 07:08:14 Age [y:d:h:m:s]: 05:140:20:25:19
Block: 43126 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1250800 RingCT/type: yes/0
Extra: 0188301f2b121d640c4c8b9e201b885639076995850b405e3578d3d2c95569cbfd0211000000244ac5aa02000000000000000000

1 output(s) for total of 441.678747526000 dcy

stealth address amount amount idx
00: bcf88a7075c95dfe3a66c960ba3e65c059f36017eae0023fd0d71278d7a81197 441.678747526000 77949 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": 43136, "vin": [ { "gen": { "height": 43126 } } ], "vout": [ { "amount": 441678747526, "target": { "key": "bcf88a7075c95dfe3a66c960ba3e65c059f36017eae0023fd0d71278d7a81197" } } ], "extra": [ 1, 136, 48, 31, 43, 18, 29, 100, 12, 76, 139, 158, 32, 27, 136, 86, 57, 7, 105, 149, 133, 11, 64, 94, 53, 120, 211, 210, 201, 85, 105, 203, 253, 2, 17, 0, 0, 0, 36, 74, 197, 170, 2, 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