Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa104952dbd3753fe0f94be06d3957900651380237f7ee6e40d8fdea9651d380

Tx prefix hash: 02aa72f75ea08268ee49623bb2f74c368ad9f6e42b114d0ce273ab1378eff0cd
Tx public key: d15901091ee9a857ff751ee2edf05b005f83b92e45f81f3b87c9c7a96f97cc30
Timestamp: 1582440746 Timestamp [UCT]: 2020-02-23 06:52:26 Age [y:d:h:m:s]: 04:352:13:11:43
Block: 70770 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1144243 RingCT/type: yes/0
Extra: 01d15901091ee9a857ff751ee2edf05b005f83b92e45f81f3b87c9c7a96f97cc300211000000017adf42d3000000000000000000

1 output(s) for total of 357.692978071000 dcy

stealth address amount amount idx
00: c15efd20167b2722f158da51e756d80a2de3af9cb08b11a0ffaedc9f0938a15d 357.692978071000 130738 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": 70780, "vin": [ { "gen": { "height": 70770 } } ], "vout": [ { "amount": 357692978071, "target": { "key": "c15efd20167b2722f158da51e756d80a2de3af9cb08b11a0ffaedc9f0938a15d" } } ], "extra": [ 1, 209, 89, 1, 9, 30, 233, 168, 87, 255, 117, 30, 226, 237, 240, 91, 0, 95, 131, 185, 46, 69, 248, 31, 59, 135, 201, 199, 169, 111, 151, 204, 48, 2, 17, 0, 0, 0, 1, 122, 223, 66, 211, 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