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: 79d0a5ed0136bc5ce69ef8d57bd5ad3b129dccae4c7e34c5ea3988c7dd331d2c
Tx prefix hash: 51639618cbf738b9a183a7ada55e5e8c6d7d887aa77ee95c9743e7bd6cef245e
Tx public key: 680c68b83c17f3b84af3d83306749776d0b01708ae3422c4cb6e021fe2f090a5
| Timestamp: 1780686188 | Timestamp [UTC]: 2026-06-05 19:03:08 | Age [y:d:h:m:s]: 00:003:09:29:54 |
| Block: 5416 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2594 | RingCT/type: yes/0 |
| Extra: 01680c68b83c17f3b84af3d83306749776d0b01708ae3422c4cb6e021fe2f090a5020900000002e49593ff00 | ||
1 output(s) for total of 34.822847425664 HMNY
| stealth address | amount | amount idx | tag |
| 00: 31b918a85b63fe86ec697c149a4cf72eb47cd1f432f0ca1876ffbd8caa824bbf | 34.822847425664 | 6853 of 0 | <8c> |
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": 5476,
"vin": [ {
"gen": {
"height": 5416
}
}
],
"vout": [ {
"amount": 34822847425664,
"target": {
"tagged_key": {
"key": "31b918a85b63fe86ec697c149a4cf72eb47cd1f432f0ca1876ffbd8caa824bbf",
"view_tag": "8c"
}
}
}
],
"extra": [ 1, 104, 12, 104, 184, 60, 23, 243, 184, 74, 243, 216, 51, 6, 116, 151, 118, 208, 176, 23, 8, 174, 52, 34, 196, 203, 110, 2, 31, 226, 240, 144, 165, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}