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: ee385343209c185506469341ed7cf7481f9d05e034132b4485ed2f69ac804571
Tx prefix hash: 86420cd811e9e9aa55a2f5e44393e382552e254dcab60abf54fdb4f5771676af
Tx public key: 0a45d1b25585cdbb23b0cea754c8351d686c1ac4da041bb47ad274ff43c40727
| Timestamp: 1780690280 | Timestamp [UTC]: 2026-06-05 20:11:20 | Age [y:d:h:m:s]: 00:003:06:29:16 |
| Block: 5648 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2249 | RingCT/type: yes/0 |
| Extra: 010a45d1b25585cdbb23b0cea754c8351d686c1ac4da041bb47ad274ff43c40727020900000001e49593ff00 | ||
1 output(s) for total of 34.807441539794 HMNY
| stealth address | amount | amount idx | tag |
| 00: 6fa6307274bcea1fd3bbcb780c0cec9745f2b95f1ef4a6725abdda571d78e3a5 | 34.807441539794 | 7097 of 0 | <92> |
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": 5708,
"vin": [ {
"gen": {
"height": 5648
}
}
],
"vout": [ {
"amount": 34807441539794,
"target": {
"tagged_key": {
"key": "6fa6307274bcea1fd3bbcb780c0cec9745f2b95f1ef4a6725abdda571d78e3a5",
"view_tag": "92"
}
}
}
],
"extra": [ 1, 10, 69, 209, 178, 85, 133, 205, 187, 35, 176, 206, 167, 84, 200, 53, 29, 104, 108, 26, 196, 218, 4, 27, 180, 122, 210, 116, 255, 67, 196, 7, 39, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}