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: 038981a3bea573fe2da6afbe02f169f90a2d4a53023b9144d8fd3f7af7c680fa
Tx prefix hash: 77c0c7d5dd15d499c83efc70abd402e6e2617f36687e92129c0187f9f723d5c0
Tx public key: 0aab2018fe1f4ae43069139a5a28ccba52953a5c359bef82b2e4bbf89e57f035
| Timestamp: 1780080081 | Timestamp [UTC]: 2026-05-29 18:41:21 | Age [y:d:h:m:s]: 00:010:06:05:26 |
| Block: 4753 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3133 | RingCT/type: yes/0 |
| Extra: 010aab2018fe1f4ae43069139a5a28ccba52953a5c359bef82b2e4bbf89e57f03502090000000126697be300 | ||
1 output(s) for total of 34.866911325618 HMNY
| stealth address | amount | amount idx | tag |
| 00: 528d997c0b34ce71c6b6e9d63baa668d0fe6a54f4fa16c89664d9f86f0234dd8 | 34.866911325618 | 5974 of 0 | <0d> |
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": 4813,
"vin": [ {
"gen": {
"height": 4753
}
}
],
"vout": [ {
"amount": 34866911325618,
"target": {
"tagged_key": {
"key": "528d997c0b34ce71c6b6e9d63baa668d0fe6a54f4fa16c89664d9f86f0234dd8",
"view_tag": "0d"
}
}
}
],
"extra": [ 1, 10, 171, 32, 24, 254, 31, 74, 228, 48, 105, 19, 154, 90, 40, 204, 186, 82, 149, 58, 92, 53, 155, 239, 130, 178, 228, 187, 248, 158, 87, 240, 53, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}