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: c393907d1fd35bbb591027ac5764cc4ac241aee3d1b93c81e12f6eed194b0c5b
Tx prefix hash: d449560d61d4d6154efc62721b41a5d98277599c1dcdcb7c4144494fc39bc75e
Tx public key: d1b9a0dcfff3b2e4b51a1f308dd621af38054b927051ef6ccd51563032bdf1a4
| Timestamp: 1779714089 | Timestamp [UTC]: 2026-05-25 13:01:29 | Age [y:d:h:m:s]: 00:014:12:34:28 |
| Block: 1610 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6276 | RingCT/type: yes/0 |
| Extra: 01d1b9a0dcfff3b2e4b51a1f308dd621af38054b927051ef6ccd51563032bdf1a4020900000001ba6d17be00 | ||
1 output(s) for total of 35.076559343127 HMNY
| stealth address | amount | amount idx | tag |
| 00: f79764ca2a4f31e78536e6d0485f03e7fdf53a303ada6f6e3cbad2cfc4115105 | 35.076559343127 | 1768 of 0 | <a0> |
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": 1670,
"vin": [ {
"gen": {
"height": 1610
}
}
],
"vout": [ {
"amount": 35076559343127,
"target": {
"tagged_key": {
"key": "f79764ca2a4f31e78536e6d0485f03e7fdf53a303ada6f6e3cbad2cfc4115105",
"view_tag": "a0"
}
}
}
],
"extra": [ 1, 209, 185, 160, 220, 255, 243, 178, 228, 181, 26, 31, 48, 141, 214, 33, 175, 56, 5, 75, 146, 112, 81, 239, 108, 205, 81, 86, 48, 50, 189, 241, 164, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}