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: 4b56972deaa62cef2de29a74e5784e88587311ed970bd2257b6a312ebd3570fb
Tx prefix hash: fd316000fa74c9c767f6f5bd17450a32fc6570bf40a8ddaac0200754f91eedd3
Tx public key: 6f9afd881432ae31e63ea58770fafe77ae19732f67e0d45a48ccbd0c1239d34a
| Timestamp: 1779981912 | Timestamp [UTC]: 2026-05-28 15:25:12 | Age [y:d:h:m:s]: 00:011:07:53:41 |
| Block: 3926 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3960 | RingCT/type: yes/0 |
| Extra: 016f9afd881432ae31e63ea58770fafe77ae19732f67e0d45a48ccbd0c1239d34a02090000000226697be300 | ||
1 output(s) for total of 34.925273452604 HMNY
| stealth address | amount | amount idx | tag |
| 00: bb58afb790a41d1143da7cb5414e1c8108a93ff5f68ce0757b87dbf941efd407 | 34.925273452604 | 4823 of 0 | <b7> |
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": 3986,
"vin": [ {
"gen": {
"height": 3926
}
}
],
"vout": [ {
"amount": 34925273452604,
"target": {
"tagged_key": {
"key": "bb58afb790a41d1143da7cb5414e1c8108a93ff5f68ce0757b87dbf941efd407",
"view_tag": "b7"
}
}
}
],
"extra": [ 1, 111, 154, 253, 136, 20, 50, 174, 49, 230, 62, 165, 135, 112, 250, 254, 119, 174, 25, 115, 47, 103, 224, 212, 90, 72, 204, 189, 12, 18, 57, 211, 74, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}