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: 03ff84c03046a3c190a523868e55fc644022fdf0ece1e948cffb6f69dd6e694b
Tx prefix hash: 8b3317689b106359b4db64bd2fadeb502f462300eb5b1928be6edd2a827c7d67
Tx public key: 07943eceb319f97a880e087b2f7b995d924f28f9323d95aae9a84839f182fd6d
| Timestamp: 1780690879 | Timestamp [UTC]: 2026-06-05 20:21:19 | Age [y:d:h:m:s]: 00:003:05:14:38 |
| Block: 5691 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2195 | RingCT/type: yes/0 |
| Extra: 0107943eceb319f97a880e087b2f7b995d924f28f9323d95aae9a84839f182fd6d020900000001e49593ff00 | ||
1 output(s) for total of 34.804586887317 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8ed0f48423c6697a1e9ee12f9b88ab08f0b9c424a37a6f183c37eae15a66ef20 | 34.804586887317 | 7142 of 0 | <34> |
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": 5751,
"vin": [ {
"gen": {
"height": 5691
}
}
],
"vout": [ {
"amount": 34804586887317,
"target": {
"tagged_key": {
"key": "8ed0f48423c6697a1e9ee12f9b88ab08f0b9c424a37a6f183c37eae15a66ef20",
"view_tag": "34"
}
}
}
],
"extra": [ 1, 7, 148, 62, 206, 179, 25, 249, 122, 136, 14, 8, 123, 47, 123, 153, 93, 146, 79, 40, 249, 50, 61, 149, 170, 233, 168, 72, 57, 241, 130, 253, 109, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}