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: 71f14861dd8008affd4c11183e945b682fe97feaa3df35ac89869c5087c96e71
Tx prefix hash: 40f720d74b1ed18589751d1486d261c800f9da3314439de029dcef568855d122
Tx public key: 955268fe3183476306a6d9f37a990b408333444d44fbbd9ea33efc523cecb5fd
| Timestamp: 1779852383 | Timestamp [UTC]: 2026-05-27 03:26:23 | Age [y:d:h:m:s]: 00:012:22:09:34 |
| Block: 2550 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5336 | RingCT/type: yes/0 |
| Extra: 01955268fe3183476306a6d9f37a990b408333444d44fbbd9ea33efc523cecb5fd02090000000126697be300 | ||
1 output(s) for total of 35.013726592842 HMNY
| stealth address | amount | amount idx | tag |
| 00: 68a37580a975275b0ee9a490575f4b67932c994fb231b0313bbd44424d5497f8 | 35.013726592842 | 3002 of 0 | <41> |
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": 2610,
"vin": [ {
"gen": {
"height": 2550
}
}
],
"vout": [ {
"amount": 35013726592842,
"target": {
"tagged_key": {
"key": "68a37580a975275b0ee9a490575f4b67932c994fb231b0313bbd44424d5497f8",
"view_tag": "41"
}
}
}
],
"extra": [ 1, 149, 82, 104, 254, 49, 131, 71, 99, 6, 166, 217, 243, 122, 153, 11, 64, 131, 51, 68, 77, 68, 251, 189, 158, 163, 62, 252, 82, 60, 236, 181, 253, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}