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: 47131485dd951e938f435422ea8acffca91ac1b10ee45046e26e33612bd6238d
Tx prefix hash: f1a72233289a56e0cc1b39e385ebd135004b469c64567cd26da7ea491006e308
Tx public key: 394c7b12abcffd53766ec8afee7843c3ed473bc9832abf461535ad4c94b84ded
| Timestamp: 1780755528 | Timestamp [UTC]: 2026-06-06 14:18:48 | Age [y:d:h:m:s]: 00:002:11:17:09 |
| Block: 6530 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1356 | RingCT/type: yes/0 |
| Extra: 01394c7b12abcffd53766ec8afee7843c3ed473bc9832abf461535ad4c94b84ded020900000003e49593ff00 | ||
1 output(s) for total of 34.748934795441 HMNY
| stealth address | amount | amount idx | tag |
| 00: fa921b3b4507f6f48fd8d10c60ac1fddb221a8fd6619e1315c1ecf42357ecbb6 | 34.748934795441 | 8032 of 0 | <67> |
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": 6590,
"vin": [ {
"gen": {
"height": 6530
}
}
],
"vout": [ {
"amount": 34748934795441,
"target": {
"tagged_key": {
"key": "fa921b3b4507f6f48fd8d10c60ac1fddb221a8fd6619e1315c1ecf42357ecbb6",
"view_tag": "67"
}
}
}
],
"extra": [ 1, 57, 76, 123, 18, 171, 207, 253, 83, 118, 110, 200, 175, 238, 120, 67, 195, 237, 71, 59, 201, 131, 42, 191, 70, 21, 53, 173, 76, 148, 184, 77, 237, 2, 9, 0, 0, 0, 3, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}