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: f71169da72e64848ea163a7654ed60055377f7fb8137143011e177bac3d1f9fd
Tx prefix hash: d578febbf0d180c3b0d49195e014befffb99781a47c8edd658c17d50ad46cffd
Tx public key: 925bd435dbbc2ad12f0b0fe6bf45f52f6bc772b5677c852ae6f9b5bdc917fea8
| Timestamp: 1780322932 | Timestamp [UTC]: 2026-06-01 14:08:52 | Age [y:d:h:m:s]: 00:007:13:42:06 |
| Block: 5032 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2920 | RingCT/type: yes/0 |
| Extra: 01925bd435dbbc2ad12f0b0fe6bf45f52f6bc772b5677c852ae6f9b5bdc917fea802090000003c26697be300 | ||
1 output(s) for total of 34.870174207706 HMNY
| stealth address | amount | amount idx | tag |
| 00: ff9ffea13e4eda380185b6e0d318e85c6f30a0164d5113756a50c19bec55cf20 | 34.870174207706 | 6405 of 0 | <d7> |
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": 5092,
"vin": [ {
"gen": {
"height": 5032
}
}
],
"vout": [ {
"amount": 34870174207706,
"target": {
"tagged_key": {
"key": "ff9ffea13e4eda380185b6e0d318e85c6f30a0164d5113756a50c19bec55cf20",
"view_tag": "d7"
}
}
}
],
"extra": [ 1, 146, 91, 212, 53, 219, 188, 42, 209, 47, 11, 15, 230, 191, 69, 245, 47, 107, 199, 114, 181, 103, 124, 133, 42, 230, 249, 181, 189, 201, 23, 254, 168, 2, 9, 0, 0, 0, 60, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}