Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d3f3033f94379a96d85e71f1b42b796100dc198f0a1bee21d40e49b3f6b47ed1

Tx prefix hash: 7656287f14a5b9c7ca473d20a356f8978cd867c63cc788264c89110e8fdc63f5
Tx public key: 7f045751881399caa07c0b279f057e18bd290eec3a53f987e26f07dfc73fc8da
Timestamp: 1580616325 Timestamp [UCT]: 2020-02-02 04:05:25 Age [y:d:h:m:s]: 04:301:04:45:06
Block: 56840 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1106605 RingCT/type: yes/0
Extra: 017f045751881399caa07c0b279f057e18bd290eec3a53f987e26f07dfc73fc8da02110000000217786bcf000000000000000000

1 output(s) for total of 397.801400304000 dcy

stealth address amount amount idx
00: c5eda5750edcac0f59ab2837cdde15af578ccb8b18065adcdd4172c94aadeff5 397.801400304000 104817 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": 56850, "vin": [ { "gen": { "height": 56840 } } ], "vout": [ { "amount": 397801400304, "target": { "key": "c5eda5750edcac0f59ab2837cdde15af578ccb8b18065adcdd4172c94aadeff5" } } ], "extra": [ 1, 127, 4, 87, 81, 136, 19, 153, 202, 160, 124, 11, 39, 159, 5, 126, 24, 189, 41, 14, 236, 58, 83, 249, 135, 226, 111, 7, 223, 199, 63, 200, 218, 2, 17, 0, 0, 0, 2, 23, 120, 107, 207, 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