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: 478ed4d98a617f4bc7e4c942ca2ab1473381108252243ff749c7aeef78b4d9da
Tx prefix hash: cc50562b44b86bd5776b885602948c398fa80b28d1def8b7aaa863f4a97e687f
Tx public key: 150abef1549f1a2377d4c77a64c89ce93fae3a8dd17ce3189727a0a0a1ae7da3
| Timestamp: 1779965688 | Timestamp [UTC]: 2026-05-28 10:54:48 | Age [y:d:h:m:s]: 00:011:14:41:09 |
| Block: 3803 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4083 | RingCT/type: yes/0 |
| Extra: 01150abef1549f1a2377d4c77a64c89ce93fae3a8dd17ce3189727a0a0a1ae7da302090000000226697be300 | ||
1 output(s) for total of 34.930146847276 HMNY
| stealth address | amount | amount idx | tag |
| 00: ce848628e755b142fb575d4c6867958b9a3cba8db0a243cb692f575057e4ec00 | 34.930146847276 | 4626 of 0 | <e5> |
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": 3863,
"vin": [ {
"gen": {
"height": 3803
}
}
],
"vout": [ {
"amount": 34930146847276,
"target": {
"tagged_key": {
"key": "ce848628e755b142fb575d4c6867958b9a3cba8db0a243cb692f575057e4ec00",
"view_tag": "e5"
}
}
}
],
"extra": [ 1, 21, 10, 190, 241, 84, 159, 26, 35, 119, 212, 199, 122, 100, 200, 156, 233, 63, 174, 58, 141, 209, 124, 227, 24, 151, 39, 160, 160, 161, 174, 125, 163, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}