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: 970cbbcb2c744f52df2ad294f3c89f33ada47cc76595a6af007003ccd651ab4f
Tx prefix hash: 52dbdd68212e5ce8739690566702d356de0656d7787d6517fd94fd5571af2eb8
Tx public key: 7694518dc4e0eb182cd8925dc5d1d0977aae0bf4d0d2cd7d03680d51d7b752e7
| Timestamp: 1780322700 | Timestamp [UTC]: 2026-06-01 14:05:00 | Age [y:d:h:m:s]: 00:007:10:41:47 |
| Block: 5008 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2878 | RingCT/type: yes/0 |
| Extra: 017694518dc4e0eb182cd8925dc5d1d0977aae0bf4d0d2cd7d03680d51d7b752e702090000001e26697be300 | ||
1 output(s) for total of 34.849957077146 HMNY
| stealth address | amount | amount idx | tag |
| 00: 66e36fda3dc284f1ebe9d122f7cd81caaa0a5dc6ba520cebedfa78b51927e83a | 34.849957077146 | 6381 of 0 | <d2> |
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": 5068,
"vin": [ {
"gen": {
"height": 5008
}
}
],
"vout": [ {
"amount": 34849957077146,
"target": {
"tagged_key": {
"key": "66e36fda3dc284f1ebe9d122f7cd81caaa0a5dc6ba520cebedfa78b51927e83a",
"view_tag": "d2"
}
}
}
],
"extra": [ 1, 118, 148, 81, 141, 196, 224, 235, 24, 44, 216, 146, 93, 197, 209, 208, 151, 122, 174, 11, 244, 208, 210, 205, 125, 3, 104, 13, 81, 215, 183, 82, 231, 2, 9, 0, 0, 0, 30, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}