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: db72a37f642aefe2059de5d103d8b2d90486e29d2c931e206f000156c27afeec
Tx prefix hash: 851688c59669046ed7df86fa215393ec330f220fdf82cb7f5ad8dbbbf517cbe7
Tx public key: 23e3d4e2d26f02a5e1651f8a3588a8dc23d6a012d05421409d63af1e23367ef0
| Timestamp: 1779434905 | Timestamp [UTC]: 2026-05-22 07:28:25 | Age [y:d:h:m:s]: 00:017:19:12:11 |
| Block: 109 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0918 kB |
| Tx version: 2 | No of confirmations: 7787 | RingCT/type: yes/0 |
| Extra: 0123e3d4e2d26f02a5e1651f8a3588a8dc23d6a012d05421409d63af1e23367ef0020900000001a662ed0300 | ||
1 output(s) for total of 35.177125071167 HMNY
| stealth address | amount | amount idx | tag |
| 00: c346a8a6b1f83ffc16beb784f7bd1b20026c8d5209c63bf583c3d8246d38ec55 | 35.177125071167 | 105 of 0 | <74> |
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": 169,
"vin": [ {
"gen": {
"height": 109
}
}
],
"vout": [ {
"amount": 35177125071167,
"target": {
"tagged_key": {
"key": "c346a8a6b1f83ffc16beb784f7bd1b20026c8d5209c63bf583c3d8246d38ec55",
"view_tag": "74"
}
}
}
],
"extra": [ 1, 35, 227, 212, 226, 210, 111, 2, 165, 225, 101, 31, 138, 53, 136, 168, 220, 35, 214, 160, 18, 208, 84, 33, 64, 157, 99, 175, 30, 35, 54, 126, 240, 2, 9, 0, 0, 0, 1, 166, 98, 237, 3, 0
],
"rct_signatures": {
"type": 0
}
}