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: 9c6f1130bb8dd690b283e7af3ffe675723a0b512375e8e8f9273f1a5bdcbd20b
Tx prefix hash: 2cb831c8b1dcecf20fa3d54a8a3ab5f10c3b7a28b39c45315c4b39f1569145f6
Tx public key: 5c3b23fd80da76ae910e112915c28161855bfe35b65a2c065a91c1dd4b3ed390
| Timestamp: 1780687339 | Timestamp [UTC]: 2026-06-05 19:22:19 | Age [y:d:h:m:s]: 00:003:08:16:31 |
| Block: 5477 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2473 | RingCT/type: yes/0 |
| Extra: 015c3b23fd80da76ae910e112915c28161855bfe35b65a2c065a91c1dd4b3ed390020900000001e49593ff00 | ||
1 output(s) for total of 34.818796079552 HMNY
| stealth address | amount | amount idx | tag |
| 00: 140530aab292be24e128582540afb3dc76b2e25736f04f3971e1181850a8531c | 34.818796079552 | 6916 of 0 | <6f> |
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": 5537,
"vin": [ {
"gen": {
"height": 5477
}
}
],
"vout": [ {
"amount": 34818796079552,
"target": {
"tagged_key": {
"key": "140530aab292be24e128582540afb3dc76b2e25736f04f3971e1181850a8531c",
"view_tag": "6f"
}
}
}
],
"extra": [ 1, 92, 59, 35, 253, 128, 218, 118, 174, 145, 14, 17, 41, 21, 194, 129, 97, 133, 91, 254, 53, 182, 90, 44, 6, 90, 145, 193, 221, 75, 62, 211, 144, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}