For RingCT transactions, outputs' amounts are also decoded
Tx private key can be obtained using get_tx_key
command in hashmonkey-wallet-cli command line tool
Tx hash: f60c260ae4a8df0f303bce7cfee2742c5390e700bf6f7168d465ea7a378ce95b
Tx prefix hash: f20f5dcfcfdcbe6dff49e84edc21920ef2024f6995efd83043061841b23d818b
Tx public key: 6f7dc03f86340e8df15c4957c3aa75b37b8550bed0e308c098d47691c49e4dbc
| Timestamp: 1780759243 | Timestamp [UTC]: 2026-06-06 15:20:43 | Age [y:d:h:m:s]: 00:002:10:15:14 |
| Block: 6556 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1330 | RingCT/type: yes/0 |
| Extra: 016f7dc03f86340e8df15c4957c3aa75b37b8550bed0e308c098d47691c49e4dbc020900000001e49593ff00 | ||
1 output(s) for total of 34.751434399861 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2252cfc97c2f9dd138b5097734e0d728b9f8f265be6f1964ad0fabfb728a33de | 34.751434399861 | 8070 of 0 | <ba> |
Check which outputs belong to given HMNY 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 HMNY in this transaction
Tx private key can be obtained using get_tx_key
command in hashmonkey-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": 6616,
"vin": [ {
"gen": {
"height": 6556
}
}
],
"vout": [ {
"amount": 34751434399861,
"target": {
"tagged_key": {
"key": "2252cfc97c2f9dd138b5097734e0d728b9f8f265be6f1964ad0fabfb728a33de",
"view_tag": "ba"
}
}
}
],
"extra": [ 1, 111, 125, 192, 63, 134, 52, 14, 141, 241, 92, 73, 87, 195, 170, 117, 179, 123, 133, 80, 190, 208, 227, 8, 192, 152, 212, 118, 145, 196, 158, 77, 188, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}