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: c44673b47771bb498b47a1e89ee08db1aca2a3d83104b76a68d0388b0cb224aa
Tx prefix hash: 1fdf016c265469b51282db6e1387b0c2afa6851d31fd4ccd3b4af3e77391af1d
Tx public key: 027a3a05eea3315aed541d583b90a8c0ed5a75cabc78d1a7f2de2984d87a97e9
| Timestamp: 1780904343 | Timestamp [UTC]: 2026-06-08 07:39:03 | Age [y:d:h:m:s]: 00:000:14:45:46 |
| Block: 7850 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 36 | RingCT/type: yes/0 |
| Extra: 01027a3a05eea3315aed541d583b90a8c0ed5a75cabc78d1a7f2de2984d87a97e90209000000024a728a4c00 | ||
1 output(s) for total of 34.661557353447 HMNY
| stealth address | amount | amount idx | tag |
| 00: 78df5d97cd20bf02d8f7506446439aba75304d1cf7ce69fcf678b2c245233e52 | 34.661557353447 | 9732 of 0 | <6c> |
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": 7910,
"vin": [ {
"gen": {
"height": 7850
}
}
],
"vout": [ {
"amount": 34661557353447,
"target": {
"tagged_key": {
"key": "78df5d97cd20bf02d8f7506446439aba75304d1cf7ce69fcf678b2c245233e52",
"view_tag": "6c"
}
}
}
],
"extra": [ 1, 2, 122, 58, 5, 238, 163, 49, 90, 237, 84, 29, 88, 59, 144, 168, 192, 237, 90, 117, 202, 188, 120, 209, 167, 242, 222, 41, 132, 216, 122, 151, 233, 2, 9, 0, 0, 0, 2, 74, 114, 138, 76, 0
],
"rct_signatures": {
"type": 0
}
}