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: 4647f2a84cc1a600c3f539f71806acfec8db461fc325b1fd55fed455dea1f6cd
Tx prefix hash: a644ca1c8743bbbcdaff854a1f9f4e7ab72f2079d026dca0fa72fe78221651f0
Tx public key: 2fd469818fcb98d6f7430d619602652f4fe3467526b709ed38afb12ee1cf8201
| Timestamp: 1779436590 | Timestamp [UTC]: 2026-05-22 07:56:30 | Age [y:d:h:m:s]: 00:017:19:42:20 |
| Block: 142 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7800 | RingCT/type: yes/0 |
| Extra: 012fd469818fcb98d6f7430d619602652f4fe3467526b709ed38afb12ee1cf8201020900000001a662ed0300 | ||
1 output(s) for total of 35.174911002370 HMNY
| stealth address | amount | amount idx | tag |
| 00: c124228e6e5dd6f840ec6c5cbcba9e729376b8a535619ebb6eb0e2ebe3e41ca2 | 35.174911002370 | 138 of 0 | <a2> |
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": 202,
"vin": [ {
"gen": {
"height": 142
}
}
],
"vout": [ {
"amount": 35174911002370,
"target": {
"tagged_key": {
"key": "c124228e6e5dd6f840ec6c5cbcba9e729376b8a535619ebb6eb0e2ebe3e41ca2",
"view_tag": "a2"
}
}
}
],
"extra": [ 1, 47, 212, 105, 129, 143, 203, 152, 214, 247, 67, 13, 97, 150, 2, 101, 47, 79, 227, 70, 117, 38, 183, 9, 237, 56, 175, 177, 46, 225, 207, 130, 1, 2, 9, 0, 0, 0, 1, 166, 98, 237, 3, 0
],
"rct_signatures": {
"type": 0
}
}