Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2338ce0a3f5d79933b55917d8269d8f11aaa6c2a7b7cce1bf063c42d61216abf

Tx prefix hash: 8ba2db8d7008966d3c707beaebf2b0692a9c301e9c30b02be47982bcdeaf4b2b
Tx public key: 42a646c428c8a6e5a1eda06f6f824bb74c48ebae89628954da29e08c112d4db7
Timestamp: 1583004836 Timestamp [UCT]: 2020-02-29 19:33:56 Age [y:d:h:m:s]: 05:041:23:27:11
Block: 74343 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1184263 RingCT/type: yes/0
Extra: 0142a646c428c8a6e5a1eda06f6f824bb74c48ebae89628954da29e08c112d4db70211000002cb7adf42d3000000000000000000

1 output(s) for total of 348.073995097000 dcy

stealth address amount amount idx
00: 33838a3c0aa212f98c19009e2fda6ef9fc7ed8e0c4e3e967599f110850fc7705 348.073995097000 137527 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": 74353, "vin": [ { "gen": { "height": 74343 } } ], "vout": [ { "amount": 348073995097, "target": { "key": "33838a3c0aa212f98c19009e2fda6ef9fc7ed8e0c4e3e967599f110850fc7705" } } ], "extra": [ 1, 66, 166, 70, 196, 40, 200, 166, 229, 161, 237, 160, 111, 111, 130, 75, 183, 76, 72, 235, 174, 137, 98, 137, 84, 218, 41, 224, 140, 17, 45, 77, 183, 2, 17, 0, 0, 2, 203, 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