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: f14f753f5a9f7275898b741791e9f6805b16f47f53edc7a84c11af63c458f723
Tx prefix hash: 0bb1e4663b73e3439806b02d7f1a6acbfe91b4e8078d703cb835a3befacddee2
Tx public key: 9e7c62c24f68cbca612394376d8cf1d6ac801ec6dcfe8acc418daab2777e4bf2
| Timestamp: 1780809296 | Timestamp [UTC]: 2026-06-07 05:14:56 | Age [y:d:h:m:s]: 00:001:21:34:52 |
| Block: 6998 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 911 | RingCT/type: yes/0 |
| Extra: 019e7c62c24f68cbca612394376d8cf1d6ac801ec6dcfe8acc418daab2777e4bf2020900000002e49593ff00 | ||
1 output(s) for total of 34.717930345853 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2613058feb399ad4200cc9ef77161b328ffc06c213bd5c62344c33fafe8fbcd3 | 34.717930345853 | 8630 of 0 | <1a> |
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": 7058,
"vin": [ {
"gen": {
"height": 6998
}
}
],
"vout": [ {
"amount": 34717930345853,
"target": {
"tagged_key": {
"key": "2613058feb399ad4200cc9ef77161b328ffc06c213bd5c62344c33fafe8fbcd3",
"view_tag": "1a"
}
}
}
],
"extra": [ 1, 158, 124, 98, 194, 79, 104, 203, 202, 97, 35, 148, 55, 109, 140, 241, 214, 172, 128, 30, 198, 220, 254, 138, 204, 65, 141, 170, 178, 119, 126, 75, 242, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}