Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d3ad8678724146ed98d97e328d09840086858549e6c8490e7448dc892690f8db

Tx prefix hash: 1338fcfef07075a5e841ea6190119cd49fe121f8539c4e9ed7a948116e1288ef
Tx public key: 27410df183e72b4b389fbf0b07101e52d279d93f3680a4f0d8bf809d67685082
Timestamp: 1577560838 Timestamp [UCT]: 2019-12-28 19:20:38 Age [y:d:h:m:s]: 04:325:23:48:44
Block: 33752 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1122125 RingCT/type: yes/0
Extra: 0127410df183e72b4b389fbf0b07101e52d279d93f3680a4f0d8bf809d6768508202110000001ce39b962a000000000000000000

1 output(s) for total of 474.423802071000 dcy

stealth address amount amount idx
00: 6562be6991ecae8aca620cf0cd2da24613c29e2ff81aca8bf24ef829e35daa3c 474.423802071000 56621 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": 33762, "vin": [ { "gen": { "height": 33752 } } ], "vout": [ { "amount": 474423802071, "target": { "key": "6562be6991ecae8aca620cf0cd2da24613c29e2ff81aca8bf24ef829e35daa3c" } } ], "extra": [ 1, 39, 65, 13, 241, 131, 231, 43, 75, 56, 159, 191, 11, 7, 16, 30, 82, 210, 121, 217, 63, 54, 128, 164, 240, 216, 191, 128, 157, 103, 104, 80, 130, 2, 17, 0, 0, 0, 28, 227, 155, 150, 42, 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