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: c270e3465ba63ffc56503e8e86da9d7ce7cc7eaa6a8106aa941feebbd5907451
Tx prefix hash: 48a57f041254eb6979dec4f1345281662970953d3d82e1f9e1a06feb910686a4
Tx public key: c18f21d89dbcd9606fb3bfbf16b7f375cf05f3fe15a2ed071435296bb29c7471
| Timestamp: 1780068294 | Timestamp [UTC]: 2026-05-29 15:24:54 | Age [y:d:h:m:s]: 00:010:07:53:59 |
| Block: 4614 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3272 | RingCT/type: yes/0 |
| Extra: 01c18f21d89dbcd9606fb3bfbf16b7f375cf05f3fe15a2ed071435296bb29c747102090000000226697be300 | ||
1 output(s) for total of 34.876156526367 HMNY
| stealth address | amount | amount idx | tag |
| 00: 6a3e5161e8eb059a7f4c52c45a340fcf006b6e0b65fd3a00a3445917b7dcbdf5 | 34.876156526367 | 5793 of 0 | <99> |
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": 4674,
"vin": [ {
"gen": {
"height": 4614
}
}
],
"vout": [ {
"amount": 34876156526367,
"target": {
"tagged_key": {
"key": "6a3e5161e8eb059a7f4c52c45a340fcf006b6e0b65fd3a00a3445917b7dcbdf5",
"view_tag": "99"
}
}
}
],
"extra": [ 1, 193, 143, 33, 216, 157, 188, 217, 96, 111, 179, 191, 191, 22, 183, 243, 117, 207, 5, 243, 254, 21, 162, 237, 7, 20, 53, 41, 107, 178, 156, 116, 113, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}